You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if we can some optional exceptions while running terraform destroy on a module. My use case:
I have Jenkins Module which backs/restore to a specified bucket/object in S3. Since this bucket/object is unique, I am also creating it thru the module itself. Now, if I destroy the module it also destroys the buckets as well.
The text was updated successfully, but these errors were encountered:
I think we would likely implement this as a facet of what was requested in #2253, which might come as part of #4149. Given a generic exclusion mechanism I think we would get destroy exclusion "for free", so I'm going to close this one and just consider this part of the scope of one of the others here.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 14, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if we can some optional exceptions while running
terraform destroy
on a module. My use case:I have Jenkins Module which backs/restore to a specified bucket/object in S3. Since this bucket/object is unique, I am also creating it thru the module itself. Now, if I destroy the module it also destroys the buckets as well.
The text was updated successfully, but these errors were encountered: