Forged in Fire
Docs
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
Developers / 04

Source Install.Documented Steps.

cfn-forge is currently a Python 3.12+ developer preview distributed through its public GitHub repository with a requirements file and an editable package entry point.

ServerCLI manifest
Python 3.12+Runtime
0.1.0Package version
2Targets: infra / pipeline
Installation

Six commands.
A visible toolchain.

Install the declared requirements before the editable package. The current pyproject exposes the forge command but does not yet declare runtime dependencies itself.

Current distribution. There is no packaged binary, PyPI release, license gate, or hosted installer in the repository today.

CLIInstall cfn-forge
01$ git clone https://github.com/MJ66GA-Projects/cfn-forge.git02$ cd cfn-forge03$ python3 -m venv .venv04$ source .venv/bin/activate05$ pip install -r requirements.txt06$ pip install -e .07$ forge -h
Project topology

Configuration stays
with the project.

A project-owned deployment.yaml maps environment names into external infrastructure and pipeline deployment configs. Forge remains the engine, not the owner of your environment definitions.

cfn-forgeDeployment engine
reads
deployment.yamlEnvironment topology
resolves
deployment-configs/Infra + pipeline config
writes
.forge/Stages + history
CLICurrent command surface
stage      Analyze desired state and save a releaseable stageinspect    Examine the exact staged deploymentstatus     Show current lifecycle statusrelease    Execute the staged CloudFormation Change Setdiscard    Delete and abandon the current stagerestage    Recreate a stage from current or historical context
Lifecyclestageinspectstatusreleasediscardrestage
Recordslisthistorycleanup
Advanced previewdriftreconcilerefactor (infra)teardown
Targetsinfrapipeline
First release path

Stage first.
Release separately.

  1. 01

    Configure an environment and AWS profile in the consuming deployment project.

  2. 02

    Run forge stage infra -e ENV to validate, compare, and create the stage.

  3. 03

    Run forge inspect infra -e ENV and review every artifact lane.

  4. 04

    Run forge release infra -e ENV only when the staged identity is correct.