-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azurerm_storage_management_policy (2.66 crash) #12476
Comments
I've encountered the exact same issue on Terraform v0.15.0 with the azurerm plugins with both ~2.44.0 and =2.66.0 versions. I run MacOS version 11.4 (BigSur). |
Same for me. After upgrading from 2.63 -> 2.66. Here is the output
|
Same for me, terraform v1.0.1 provider 2.66.0 Error received when updating existing state, deployment of management policy previously worked with no issue Error also refers to arm template deployments, however I think this is simply because the plugin crashes during management policy which is before arm deploy completes, so it brings the arm deploy down with it EDIT: reverting back to provider version 2.63.0 'fixes' the issue
|
2.63.0 does work, thanks @hmb133 ! |
Related to #12473. The problem is probably in the new terraform-plugin-sdk version used in 2.66.0. I reported it to the maintainers, hope to hear more today. |
This functionality has been released in v2.67.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! |
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. |
Community Note
Terraform (and AzureRM Provider) Version
terraform 1.0.1
azurerm 2.66.0
Affected Resource(s)
resource
azurerm_storage_management_policy
Terraform Configuration Files
Panic Output
Steps to Reproduce
When creating a new resource: terraform apply
Crashes as well when refreshing the state of an existing resource.
PS: Sorry for the bad formatting and everything, never used github before.
The text was updated successfully, but these errors were encountered: