Expand description
Deploy a bundle into an environment via the env-apply engine.
greentic-setup env-deploy <BUNDLE> synthesizes a
greentic.env-manifest.v1 document from a .gtbundle archive (or
bundle directory) and routes it through the deployer’s idempotent
env-apply engine — the same engine behind gtc op env apply. The
bundle’s declared bundle_id is read from the archive metadata, not
inferred from the filename (see module-level doc on “the bundle_id
trap”).
§The bundle_id trap
Multiple .gtbundle filenames can declare the same bundle_id in
their metadata (e.g. quickstart-rich.gtbundle and
quickstart-rich-v2.gtbundle both declare bundle_id: quickstart-bundle). Using the filename stem instead of the declared
id would create a second deployment instead of converging on /
blue-greening the existing one, breaking the idempotency contract.
Functions§
- deploy_
bundle_ to_ env - Deploy a bundle into an environment.