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
Since the account type can't be updated, I expected terraform to replace the resource instead.
Actual Behavior
What actually happened?
* module.workers.azurerm_storage_account.tectonic_worker: 1 error(s) occurred:
* azurerm_storage_account.tectonic_worker: Error updating Azure Storage Account type "c99c88ef": storage.AccountsClient#Update: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="StorageAccountTypeConversionNotAllowed" Message="Storage account type cannot be changed to Premium_LRS."
Steps to Reproduce
Create a Standard_LRS storage account with terraform and terraform apply
Change the tier to Premium_LRS storage account and terraform apply
The text was updated successfully, but these errors were encountered:
- Support for File Encryption. Fixes#80
- Adding Import tests
- Support for Custom Domains on Storage Accounts. Fixes#15
- Splitting the storage account Tier and Replication out into separate fields. Incorporating #117 & Fixing #110
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!
ghost
locked and limited conversation to collaborators
Apr 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue was originally opened by @discordianfish as hashicorp/terraform-provider-azure-classic#27. The original body of the issue is below.
Terraform Version
Affected Resource(s)
Expected Behavior
Since the account type can't be updated, I expected terraform to replace the resource instead.
Actual Behavior
What actually happened?
Steps to Reproduce
terraform apply
terraform apply
The text was updated successfully, but these errors were encountered: