-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Upgrade to 1.32.0 breaks storage table #3924
Comments
Hello |
The issue seems to be related to #3834 The construction of the id is not the same between 1.31 and 1.32. On the previous version the id is following the form Renaming the id in the tfstate or removing the whole resource and importing it seem to fix the issue seen during |
No it won't work) I tried it and got the same 'Expected the Table Name to be in the format |
hitting the same issue. i can help with testing if needed |
Hey all, thanks for opening this issue. I just merged the fix for this that will go out in the next release. Going to close this down but feel free to reopen if you continue to have issues after the next release goes out. |
This has been released in version 1.32.1 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.32.1"
}
# ... other configuration ... |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
After upgrading to 1.32.0 refreshing an existing storage table fails with the error
Expected the Table Name to be in the format 'Tables('name')' but got "test"
Creating a new storage table from scratch works
Repro: apply the following config
The change the provider version to
1.32.0
and run apply again:The text was updated successfully, but these errors were encountered: