| name | atmos-demo-bump |
| description | Use when demoing Atmos Pro / Terraform plan changes on this repo's mock components — bumping a `<component>_version` or `name` in a stack to produce a visible plan diff, wiring up a mock component with the version-bump pattern (random_id keepers + null_resource triggers), or replaying a demo via an empty commit. Triggered by requests like "bump the cluster version", "bump the <x> name", plain "bump it", "set up the <x> component so I can demo a change", "why does the plan show no infrastructure changes", or "add triggers to component X". |
Atmos Demo Bump
This repo is an Atmos Pro example. The Terraform components under components/terraform/ (except dynamodb, which is a real AWS module) are mocks — they only manage random_id resources. To make a plan show a real infrastructure change during a demo, each component exposes a <component>_version input variable, and that variable is wired to random_id.keepers and a null_resource.triggers. Bumping the version in a stack forces recreates, which surfaces as real plan lines (not just output-only diffs).
What this skill covers
- Bumping a version — produce a visible plan change in a specific stack.
- Bumping a name — increment the numeric suffix on
name (e.g. cluster25 → cluster26) to force a new random_id and all downstream recreates.
- Just "bump it" — push another empty commit to replay CI/Atmos Pro on the current state.
- Wiring a component — add the demo pattern to a new or existing mock component.
1. Bumping a version
Goal: user asks something like "bump the cluster version in dev" or "demo a change on frontend in staging." You need to produce a Terraform plan that shows real replacements, not just .
