Importing infrastructure in the console
Turn Terraform, CloudFormation, Kubernetes or Docker Compose files into a draft OrkStage template, review the evidence and create the template.
Templates, then Import, turns existing infrastructure code into a draft template. The
OrkStage scan engine detects and maps the resources. It is the same engine the ork CLI uses.
Two ways in
Choose a folder or individual files. The console keeps only the text files the engine understands,
such as .tf, .tf.json, YAML, JSON, TOML, Dockerfile, package.json, go.mod,
requirements.txt and Chart.yaml. It skips the node_modules, .git, .terraform, .next,
target, vendor, dist and build folders. Each file can be at most 512 KiB, and the upload at
most 5 MB in total. The server scans the files with the engine compiled to WebAssembly
(@orkstage/scan).
If the server answers 501 SCANNER_UNAVAILABLE, scanning is not installed on that server. Scan
locally with the CLI instead.
Reviewing the result
The import page shows five things:
- Resources: each detected resource with its OrkStage type, provider, implementation,
confidence (
high,mediumorlow) and the source evidence, such asmain.tf:12 aws_db_instance.main. - Connections inferred from references, for example a task definition that reads the database address.
- Unmapped items: what the engine saw but cannot express in a template, with the reason.
- Warnings and the validation result of the generated template.
- The generated template YAML.
Creating the template
Give the template a name and a display name, then click Create draft and open builder.
OrkStage creates a DRAFT template at version 0.1.0 and opens it in the builder. Fix what the
validation reported, then publish it.
Each import produces at most one template. Only platform owners and admins can create templates. Other users see a note asking them to share the import id with a platform admin.
See Importing IaC for supported sources, mapping rules and the API.
Template marketplace
Browse curated and community templates with review badges, see their resources and cost before you deploy, and submit your own templates for review.
Roles and permissions
The seven predefined OrkStage roles (three for the platform, four per tenant), what each can do, and how every request enforces tenant isolation.