fix: Fix deletion protection for Azure storage #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is not possible lock the container, only Storage accounts
https://learn.microsoft.com/en-us/azure/storage/common/lock-account-resource?tabs=portal
To protect the container, broader research must determine if using an
Immutability policy on a container
can resolve this topic.https://learn.microsoft.com/en-us/azure/storage/blobs/data-protection-overview
But Terraform AzureRM don't support container immutability policies yet.
hashicorp/terraform-provider-azurerm#3722
In the same issue above, there's a solution based on
az_api
provider that eventually can help if the solution isImmutability policy