Combine CloudFormation resource actions with nested template trees, body-level diffs, parameter provenance, dependencies, lifecycle state, and release readiness.
These capabilities are present in the current source and form the product’s core marketing surface.
Validate parameters, resolve the environment, upload the desired template tree, and create a CloudFormation Change Set without touching production.
A local stage artifact preserves the exact stack, environment, region, Change Set, resource summary, template diffs, and lifecycle state.Compare deployed and desired nested templates by presence, SHA-256, and normalized body—not just the root stack summary.
Forge surfaces added, removed, and modified templates alongside unified body diffs for the files that actually changed.Trace parameter changes through nested-stack updates and connect one changed input to the resources and stacks it affects.
Inspect the old value, new value, dependent outputs, nested stack impact, and CloudFormation action in one release artifact.Revalidate the staged Change Set, require operator confirmation, execute, wait for completion, and capture outputs and failure events.
Identity checks guard stack, environment, and region before Forge moves a stage from STAGED to RELEASING and RELEASED or FAILED.List, inspect, discard, restage, clean up, and review the history of deployment artifacts stored under the project-owned .forge workspace.
Stages become identifiable records with timestamps and state transitions instead of transient terminal output.Use the same stage, inspect, status, release, discard, restage, history, and cleanup grammar for infrastructure and pipeline stacks.
Separate configuration and orchestrators preserve target-specific AWS identity while keeping the operator workflow consistent.
01$ forge inspect infra -e dev1-us02 03Current CloudFormation Template Tree:04 Networking.yaml: 178a26f9b78105 Root.yaml: 75c9be241ac406 Telemetry.yaml: 0ce33d7fae6107 08Desired Template Tree:09 Networking.yaml: 61ac7e128bd210 Root.yaml: 75c9be241ac411 Telemetry.yaml: dca14502bcd8Forge hashes every template in the deployed and desired trees, emits unified body diffs, retains CloudFormation actions, and connects changed parameters to affected nested stacks.
These systems exist in the current engine but remain intentionally labeled preview while their policies and supported strategies expand.
Walk nested stacks and separate expected runtime variance from actionable CloudFormation drift.
Classify changes as safe, review, destructive, or undetermined and execute only a narrowly supported safe strategy.
Score template trees for hardcoded accounts, regions, environments, repeated configuration, stale parameters, and duplicate conditions.
Inventory resources and nested stacks, expose termination protection, require an exact-name confirmation, and report deletion failures.
Truthful by default. Promotion, provider-independent deployment, hosted API access, and automatic broad reconciliation are roadmap directions—not current product claims.