Forged in Fire
Workflows
Heating the forge
Heat / Shape / Strike
CloudFormationCLINested Template DiffsTerraformAIChange Set StagingCI / CD PipelinesParameter ImpactNext.js ApplicationsRelease InspectionInfrastructure as CodeLifecycle HistoryAWS EnvironmentsRelease GuardrailsAPIRefactor AnalysisDrift IntelligenceTeardown Planning
Forge logoForge
Sign inRegisterDownload
Workflows / 03

Deploy Cycle.CLI Commands.

Forge separates analysis from execution, gives every stage an identity, and preserves the release outcome so operators can inspect the exact artifact they are approving.

Run the quickstartGet the source
STAGEDBefore execution
RELEASINGDuring execution
RELEASEDRecorded outcome
The controlled path

Four moments.
One artifact.

Each command advances or interrogates a durable stage instead of hiding the deployment decision inside one operation.

  1. 01
    Stageforge stage infra -e dev1-us

    Resolve topology, validate parameters, compare template trees, build a Change Set, and save the artifact.

  2. 02
    Inspectforge inspect infra -e dev1-us

    Review resource actions, template bodies, dependencies, parameter impact, counts, and release readiness.

  3. 03
    Releaseforge release infra -e dev1-us

    Confirm the exact staged deployment, execute it, wait for CloudFormation, and record the result.

  4. 04
    Rememberforge history infra

    Keep the stage lifecycle available for status, history, restage, discard, and cleanup operations.

Target / Infra

Infrastructure

Stage and release nested application infrastructure with template-tree, body-diff, parameter-impact, and dependency context.

forge stage infra -e dev1-us
Target / Pipeline

Pipelines

Apply the same lifecycle grammar to pipeline CloudFormation stacks while retaining their separate region, profile, configuration, and stage directories.

forge stage pipeline -e dev1-us
Consistent operator grammar

Change the target.
Keep the verbs.

Infrastructure and pipeline implementations stay separate under the hood while the human interface stays familiar.

CLILifecycle command sets
01$ forge stage infra -e dev1-us02$ forge inspect infra -e dev1-us03$ forge status infra -e dev1-us04$ forge release infra -e dev1-us05$ forge history infra
STAGED→RELEASING→RELEASED
DISCARDEDSUPERSEDEDFAILED
Every exit matters

Success is not the only history worth keeping.

Discarded, superseded, and failed stages remain part of the operator record and can inform cleanup or restage decisions.