gtme freeze
Print the pipeline.yaml that produced a run, reconstructed from its stored config
What you'll learn
You're about to type gtme freeze and want its forms and its flags.
- every form of
gtme freezeand what each does - each flag and what it changes
- where the docs use it
Print the pipeline.yaml that produced a run, reconstructed from its stored config; --bundle assembles a portable campaign bundle instead (pipeline + referenced bindings with fixtures + registry slice + hash manifest), which gtme run accepts wherever it accepts a pipeline path (ADR-029)
Forms
gtme freeze [RUN_ID|last] [--bundle DIR]
Flags
| Flag | Takes | What it does |
|---|---|---|
--bundle | DIR | --bundle assembles a portable campaign bundle instead (pipeline + referenced bindings with fixtures + registry slice + hash manifest), which gtme run accepts wherever it accepts a pipeline path (ADR-029) |
It exits with one of the exit codes every verb shares.
Example
From Package and share a campaign:
gtme freeze last --bundle renewal-openers-v1
Used in
- A campaign is a folder: The command that writes a bundle, or prints a pipeline's YAML without one
- Agent-operable by design: Prints a run's exact pipeline as YAML on stdout
- Report: Prints the pipeline a run used, including the rates behind its cost avoided
- Package and share a campaign: Every form and flag of the command that writes a bundle