Skip to main content
Two offline importers turn an existing deployment definition into reviewable Levelrail documents (App kinds inside a Stack). Both are dry runs: nothing is written unless you pass --write DIR, and existing files are kept without --force.
Then run levelrail-cli stack plan NAME -f ./iac and apply as for any stack.

Secrets are references

Values are never read into the output. Every secret becomes a name listed in SECRETS.md, and the App document refers to it as a secret reference. Clear environment values that look like secrets (by name or by value) are turned into references too. Fill them at apply time with --secret NAME=env:CI_SECRET.

deploy.yml

Fields with no equivalent (registry, ssh, builder, boot, volumes, server hosts and others) are listed in the notes. Any field the importer does not know is an error that names it, so nothing is dropped silently. A file with ERB tags (<% %>) is refused: render it first.

Portainer

The input is a stack compose file or the JSON export of a stack (Name, StackFileContent, Env). Image services become Apps. Environment values and the export Env values are never read, only names. Services with a build context are skipped with a note, and volumes, command overrides and env_file entries are listed in the notes. The size limit for the input file is LEVELRAIL_IMPORT_FILE_MAX_BYTES.
Last modified on November 17, 2026