Skip to content
Discussion options

You must be logged in to vote

Do not rely on apply rollback (it does not destroy created resources). Instead wrap the workflow: run terraform apply, and on any non-zero exit run terraform destroy -auto-approve in a trap/finally. Combine with a provider-level timeout and a budget guard that polls pod uptime and force-destroys past a threshold. The idempotent destroy is what actually stops the billing, not apply semantics.

Replies: 1 comment

Comment options

iacker
Jul 10, 2026
Maintainer Author

You must be logged in to vote
0 replies
Answer selected by iacker
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant