🔨 Stack Forge

Self-Service Infrastructure Templating Engine for Terraform & Terragrunt

A CLI tool that generates production-ready Terraform and Terragrunt configurations from reusable templates. Stop writing boilerplate infrastructure code and start deploying in minutes.

⚡ 30-Second Quick Start

git clone https://github.com/pt1691/stack-forge.git && cd stack-forge
python3 -m venv .venv && source .venv/bin/activate
pip install -e .
forge list-templates  # See available templates!

That's it! Now create your first infrastructure:

mkdir my-infra && cd my-infra
forge init --name my-app --org mycompany
forge add-stack --name network --env dev
forge add-resource --stack network --name main-vpc --type vpc
forge generate  # Creates Terraform files!

✨ Features

• 🚀 Quick Setup - Generate complete infrastructure stacks with a few commands
• 📦 Pre-built Templates - VPC, EKS, S3, RDS, Lambda, and more
• 🔧 Terragrunt Support - DRY configurations with Terragrunt integration
• 🏷️ Consistent Tagging - Automatic resource tagging across all resources
• 🔒 Security Best Practices - Templates follow AWS security guidelines
• 📝 Customizable - Extend with your own templates

🚀 Installation

git clone https://github.com/pt1691/stack-forge.git
cd stack-forge
python3 -m venv .venv
source .venv/bin/activate
pip install -e .

📖 Workflow Example

# 1. Create a new project
mkdir my-platform && cd my-platform
forge init --name my-platform --org acmecorp

# 2. Add a stack (environment + resource group)
forge add-stack --name network --env dev

# 3. Add resources to the stack
forge add-resource --stack network --name main-vpc --type vpc
forge add-resource --stack network --name logs --type s3_bucket

# 4. Generate Terraform files
forge generate

# 5. Review what was created
tree infrastructure/

📋 Commands

📦 Available Templates

📁 Generated Structure

infrastructure/
├── network/
│   ├── providers.tf          # AWS provider configuration
│   ├── backend.tf            # S3 backend for state
│   ├── main.tf               # Module calls
│   ├── terragrunt.hcl        # Terragrunt configuration
│   └── modules/
│       ├── main-vpc/
│       │   ├── main.tf
│       │   ├── variables.tf
│       │   └── outputs.tf
│       └── logs/
│           ├── main.tf
│           ├── variables.tf
│           └── outputs.tf

⚙️ Configuration (forge.yaml)

version: "1.0"
name: my-platform
organization: mycompany
default_provider: aws
default_region: us-west-2
environments:
  - dev
  - staging
  - prod

stacks:
  - name: network
    environment: dev
    region: us-west-2
    use_terragrunt: true
    resources:
      - name: main-vpc
        type: vpc
        variables:
          vpc_cidr: "10.0.0.0/16"
          az_count: 3
          enable_nat_gateway: true
          
      - name: logs
        type: s3_bucket
        variables:
          versioning_enabled: true

🔧 Custom Templates

Add your own templates in ~/.stack-forge/templates/:

~/.stack-forge/templates/
└── my_custom_resource/
    ├── main.tf.j2
    ├── variables.tf.j2
    └── outputs.tf.j2

Templates use Jinja2 with these available variables:

• {{ name }} - Resource name
• {{ environment }} - Environment (dev/staging/prod)
• {{ region }} - AWS region
• {{ variables }} - Resource-specific variables
• {{ tags }} - Merged tags

📝 Best Practices

1. Use environments - Create separate stacks for dev/staging/prod
2. DRY with Terragrunt - Enable use_terragrunt: true for DRY configs
3. Consistent naming - Use descriptive stack and resource names
4. Tag everything - Define global_tags in your project config

🧪 Development

# Install dev dependencies
pip install -e ".[dev]"

# Run tests
pytest

# Run linter
ruff check .

📝 License

MIT License - see LICENSE for details.

🙋‍♂️ Author

Praneeth Turlapati

• LinkedIn: linkedin.com/in/praneeth-turlapati
• GitHub: github.com/pt1691

⭐ If you find this useful, please star the repository!