Skip to content

Issue #188: Terraform adoption baseline alignment#582

Merged
wilhel1812 merged 1 commit intostagingfrom
issue/188-terraform-adoption-fixes
Apr 9, 2026
Merged

Issue #188: Terraform adoption baseline alignment#582
wilhel1812 merged 1 commit intostagingfrom
issue/188-terraform-adoption-fixes

Conversation

@wilhel1812
Copy link
Copy Markdown
Owner

Summary

  • align Terraform staging/prod tfvars to live imported resources (zone IDs, DNS names, Access app names/policy binding)
  • update backend examples to Terraform 1.5-compatible S3 backend args for R2
  • add D1 read replication mode modeling to prevent import drift
  • keep Access application in adoption-safe mode with ignore_changes = all
  • fix local tf:validate/init --backend=false reliability by using temporary TF_DATA_DIR

Why

After live import into state, baseline plan revealed drift from placeholder/default assumptions. This PR codifies the known-good baseline so import-first rollout remains zero-diff and safe.

Verification

  • npm run tf:fmt
  • npm run tf:validate
  • npm test
  • npm run build

@wilhel1812 wilhel1812 merged commit 946cc5a into staging Apr 9, 2026
6 checks passed
@wilhel1812 wilhel1812 deleted the issue/188-terraform-adoption-fixes branch April 9, 2026 14:33
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