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
While working with existing Terraform configuration that has already been deployed, users may sometime wish to "dis-own" a particular resource, or a module, i.e. prevent Terraform from managing it but not destroy it in the process of doing so.
Previously this was done via terraform state rm and Terraform v1.7 comes with a removed {} block which provides equivalent functionality via configuration.
Background
While working with existing Terraform configuration that has already been deployed, users may sometime wish to "dis-own" a particular resource, or a module, i.e. prevent Terraform from managing it but not destroy it in the process of doing so.
Previously this was done via
terraform state rm
and Terraform v1.7 comes with aremoved {}
block which provides equivalent functionality via configuration.Users may begin with
and end up with
Proposal
removed {}
blockresource
data
module
The text was updated successfully, but these errors were encountered: