Generated Oct 14, 2026, 9:39:02 AM
Normalize tags in Terraform configs to a stable map structure before applying: e.g., use locals and 'merge' to produce a consistent map: locals { common_tags = { Environment = var.env, Owner = var.owner } }. Replace any list-style tag uses with maps. This is reversible as it’s a code change.
Pin both Terraform and provider plugin versions in required_providers and your CI environment to the same exact versions used during successful applies. Re-run 'terraform init -upgrade' in a controlled CI run to ensure provider plugin consistency.
Use 'terraform refresh' and 'terraform plan -refresh-only' to see whether diffs are from provider responses. If tfstate looks corrupted or was edited, restore from a recent state backup. Avoid manual tfstate edits; use 'terraform state' commands if needed.
As a targeted mitigation, use 'lifecycle { ignore_changes = [tags] }' on resources where tags change frequently and are not business-critical. Document this plainly — this prevents spurious recreation but can hide legitimate tag drift. Prefer normalizing tags first.
If normalization and pinning do not remove spurious replacements, collect debug logs and open an issue with the provider maintainers (include 'TF_LOG=DEBUG' outputs) or escalate within your platform team; do not apply rolling recreations in production until root cause is confirmed.