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
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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.
│ Warning: Deprecated attribute
│
│ on teleport.tf line 179, in resource "azurerm_storage_container_immutability_policy""example":
│ 179: storage_container_resource_manager_id = azurerm_storage_container.example.resource_manager_id
│
│ The attribute "resource_manager_id" is deprecated. Refer to the provider
│ documentation for details.
╵
Expected Behaviour
Terraform plan/apply successfully without any warning message
Actual Behaviour
Terraform plan/apply has show the warning message.
storage_container_resource_manager_id - (Required) The Resource Manager ID of the Storage Container where this Immutability Policy should be applied. Changing this forces a new resource to be created.
But terraform plan/apply shows warning message about deprecated attribute.
The text was updated successfully, but these errors were encountered:
@tunguyen9889 This is a warning message on the azurerm_storage_container.example.resource_manager_id. This property will be removed in v5 of the provider, and users are expected to directly use azurerm_storage_container.example.id. Though the id of azurerm_storage_container will change from the form of "https://example.blob.core.windows.net/container" to the resource manager id, only when the resource is created using the new storage_account_id. This means in your existing workspace, the id won't work.
For now, I suggest you continue using the existing configs. Since there are quite a few issues caused by #27733, and the team is reviewing and probably will introduce new changes in the near future.
Thank you for taking the time to raise this! I am going to close this with @magodo‘s response as an answer. If you have future questions, I suggest using the Community Resources, such as the Azure Provider forum.
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.
Is there an existing issue for this?
Community Note
Terraform Version
1.x
AzureRM Provider Version
4.x
Affected Resource(s)/Data Source(s)
azurerm_storage_container_immutability_policy
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Terraform plan/apply successfully without any warning message
Actual Behaviour
Terraform plan/apply has show the warning message.
Steps to Reproduce
No response
Important Factoids
No response
References
According to https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/storage_container_immutability_policy:
But terraform plan/apply shows warning message about deprecated attribute.
The text was updated successfully, but these errors were encountered: