orchestrata_ultimate.promotion

Reference › orchestrata_ultimate › promotion

Deployment — what promote has to mean.

The promotion package makes promotion mean deployment. An environment moves along the pipeline dev, test, prod; each step is gated, and a promotion to a host environment pins a commit, puts it on a separate target checkout, restarts the services, proves the result, and records the sha. The curated narrative tells why the earlier receipt-only promotion was replaced.

The stage-gating layer is the promoter, with env_profile and promoter_targets. validate refuses a profile with missing keys, hosts on the wrong subnet or unreachable Redis and graph. test refuses prod, and runs the suite pinned to the environment. promote refuses when the previous stage has not passed; for prod it needs a passing test run of the exact commit being deployed and an explicit confirmation. The ledger of results is a JSON file.

The deployment engine is the runner over the stages_* modules, re-exported by stages: stages_resolve (refuses a dirty or unpushed commit, or unreachable infrastructure), stages_tree, stages_assets (refuses non-executable hooks), stages_units, stages_verify and stages_graphs. The first failing stage stops the run; a failure after the restart triggers a rollback to the previous sha. Shared plumbing is in stages_exec, stages_context and models.

Identity verification is a separate command-line tool and the last check of verify: identity with identity_core, identity_scope, identity_checks, identity_skips and identity_urls. projects and unit_deps are small helpers. Start with the promoter, then the runner.

Curated narrative

The hand-written story of this package: orchestrata_ultimate.promotion.

23 modules, 4,089 lines of code.

Modules

Dependency diagram