Behaviour of prevent_destroy lifecycle rule

[endofcake]

Hi,

Lifecycle meta-parameter looks like it could be used to prevent some accidental destructive changes. I can set

prevent_destroy = "true"

and it does indeed cause an error if I run terraform destroy.

However, if I remove the configuration of this resource and then run terraform apply, Terraform would happily proceed to remove the resource.

Is this the intended behaviour? Should there be a way to prevent destruction of resources similar to CloudFormation stack policies? Terraform could store this setting in the state file , so that even if a resource is deleted from the configuration, Terraform would still know that it's destruction used to be explicitly denied.

Thanks.

[jbardin]

Thanks for filing the issue. We're currently tracking this in #17599

[ghost]

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.