Skip to content

docs: record proposed move from HCP to R2 state and GitHub Actions - #15

Open
hasansezertasan wants to merge 4 commits into
mainfrom
feature/r2-state-backend
Open

hasansezertasan wants to merge 4 commits into
mainfrom
feature/r2-state-backend

Conversation

@hasansezertasan

Copy link
Copy Markdown
Member

Records the decision to move Terraform state from HCP Terraform to an R2 bucket and plan/apply from HCP's VCS flow to GitHub Actions, before any code changes.

  • Moves the locked-decisions table from CLAUDE.md to .infra-copilot/decisions.md, with a status per row; the HCP rows stay locked until each leaf cuts over.
  • Adds the new direction as proposed: R2 backend with use_lockfile, post-apply state backups (R2 has no versioning), read-only plan credentials at repo level and write credentials in terraform-<leaf> environments, auto-apply on merge, an allow-destroy opt-in for deletes, and a single aggregate plan required check.
  • Moves the plugin config to .infra-copilot/config.md, unchanged.
  • Pins the toolchain in mise.toml + mise.lock, and CI installs Terraform from it instead of a second hard-coded 1.9.8.

No infrastructure changes; HCP speculative plans should show no changes on both leaves.

Move the locked-decisions table from CLAUDE.md into .infra-copilot/decisions.md
with a status per row, and move the plugin config from .claude/infra-copilot.local.md
to .infra-copilot/config.md unchanged. Record the R2 backend, Actions plan/apply,
split plan/apply credentials, auto-apply on merge, state backups, and the
destructive-apply opt-in as proposed; the HCP rows stay locked until each leaf
cuts over.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant