azurerm_resource_group: change provider feature flag prevent_deletion_if_contains_resources default to true

[katbyte]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

The default behaviour of the Azure Platform (and Terraform today) when the deleting a Resource Group is to delete all of the items within this Resource Group.

Whilst this feature makes it easy to clean-up any resources - since resources can be provisioned outside of Terraform, it means that these Resources are untracked by Terraform - and so Terraform is unable to show these Resources in the Plan during the deletion of the Resource Group.

Terraform currently has a feature-flag for this behaviour available within the Features block today - which will check during the deletion of the Resource Group for any Resources within this Resource Group, and raise an error (stating these must be removed first) if any Resources are found. In v2.x versions of the Azure Provider this is disabled by default - however for v3.0 we intend to flip this default to be enabled by default.

New or Affected Resource(s)

• azurerm_resource_group

Potential Terraform Configuration

To retain the existing behaviour the following can be used

provider "azurerm" {
  features {
    resource_group {
      prevent_deletion_if_contains_resources = false
    }
  }
}

References

• r/resource_group: feature flag for only deleting when empty / no nested resources #1608
• r/resource_group: feature flag for prevent_deletion_if_contains_resources #12657

[github-actions]

This functionality has been released in v3.0.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.