viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

cloudflared: move bridge removed{} to stack root — removed blocks are root-module-only
Some checks failed
ci/woodpecker/push/default Pipeline failed
Details

Browse source 
Pipeline 461 failed terraform init: the removed{} handoff block sat in
the stack-local module, but Terraform only allows removed blocks in the
root module. Same intent, correct position (from =
module.cloudflared.cloudflare_record.bridge_pages, destroy=false).
Without this the stale state entry would make the next cloudflared
apply destroy the record valia-sites now owns.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-07-03 12:31:53 +00:00
parent 8b80b4cc41
commit 695e020111
2 changed files with 15 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

13
stacks/cloudflared/modules/cloudflared/cloudflare.tf
View file

@ -236,16 +236,9 @@ resource "cloudflare_record" "keyserver" {
}
# bridge.viktorbarzin.me (Cloudflare Pages, "мост" school site) moved to
# stacks/valia-sites (ADR-0018) — all Valia-site records live there now.
# Forget from this state WITHOUT destroying; valia-sites imports the live
# record by id. Delete this block once both stacks have applied.
removed {
from = cloudflare_record.bridge_pages
lifecycle {
destroy = false
}
}
# stacks/valia-sites (ADR-0018) — all Valia-site records live there now. The
# state forget lives in the STACK ROOT (../..//removed-bridge.tf): removed{}
# blocks are root-module-only.
# Enable HTTP/3 (QUIC) for Cloudflare-proxied domains
resource "cloudflare_zone_settings_override" "http3" {