Promote to production
Promote your tested changeset from dev to prod: Admiral copies changes into a new prod changeset, re-based on prod's own state, with per-env values resolved.
You have a working setup in dev: a workload wired to an infrastructure output. Promotion ships that same, tested setup to prod. Promotion is a copy, not a link: Admiral clones the changes into a new changeset in prod, re-based on prod's own state, and the per-environment values resolve against prod's variables.
1. Promote the changeset
# TODO: confirm the promote/copy verb and target-env flag.
admiral changeset promote <dev-changeset> --to demo/prod2. Review against prod and apply
The promoted changeset is reviewed against prod's own deployed state, not dev's. Plan it, check the diff, and apply.
admiral changeset plan <prod-changeset>
admiral changeset apply <prod-changeset>You're done
You connected a cluster, deployed a real workload, wired an infrastructure output into it, and promoted the whole thing from dev to prod - the core Admiral loop end to end.
Where to go next
Wire infrastructure
Compose components in Admiral: add a Terraform infrastructure component, emit an output, and feed it into your workload through the dependency graph.
Concepts Overview
The mental model behind Admiral: the resources you work with, how applications, environments, and components nest, and how a change becomes a live deployment.