Files
vim-ale/terramate
AJ ONeal 9f28505af7 ref: delete unreachable upstream-fetcher modules
Stacked on the modifications PR. Now that no live code path references
the per-package fetchers, the shared HTTP/parsing helpers, the
in-process normalizer, or the example template, delete them. Pure
deletion — no behavior change.

- ~93 per-package <pkg>/releases.js fetcher modules.
- _common/{brew,fetcher,git-tag,gitea,github,github-source,
  githubish,githubish-source}.js shared HTTP/parsing helpers.
- _webi/normalize.js in-process normalization layer (cache files
  arrive normalized from webicached).
- _example/releases.js fetcher template for new packages.

The Go cache daemon (webicached) is now the sole producer of release
metadata; the Node process never makes an upstream request.
2026-05-08 16:31:59 -06:00
..
2026-03-08 19:38:49 -06:00
2024-12-18 22:08:19 +00:00

title, homepage, tagline
title homepage tagline
Terramate https://github.com/terramate-io/terramate Terramate simplifies managing large-scale Terraform codebases

To update or switch versions, run webi terramate@stable (or @v0.11.4, @beta, etc).

Cheat Sheet

Terramate enables scalable automation for Terraform by providing a robust framework for managing multiple stacks, generating code, and executing targeted workflows.

1. Create a New Project

git init -b 'main' ./terramate-quickstart
cd ./terramate-quickstart
git commit --allow-empty -m "Initial empty commit"

2. Create a Stack

terramate create \
  --name "StackName" \
  --description "Description of the stack" \
  ./stacks/stackname/

git add ./stacks/stackname/stack.tm.hcl
git commit -m "Create a stack"

3. List Stacks

terramate list

4. Detect Changes

terramate list --changed

5. Generate Code

  1. Create a .tm.hcl file for code generation:

    cat <<EOF > ./stacks/backend.tm.hcl
    generate_hcl "backend.tf" {
      content {
        terraform {
          backend "local" {}
        }
      }
    }
    EOF
    
  2. Run the generation command:

    terramate generate
    

6. Run Terraform Commands

  • Initialize stacks:

    terramate run terraform init
    
  • Plan changes:

    terramate run terraform plan
    
  • Apply changes:

    terramate run terraform apply -auto-approve
    
  • Run commands only on changed stacks:

    terramate run --changed terraform init
    terramate run --changed terraform plan
    terramate run --changed terraform apply -auto-approve