Skip to content
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

Support replacing storage_account when changing account type #110

Closed
tombuildsstuff opened this issue Jun 15, 2017 · 1 comment · Fixed by #363
Closed

Support replacing storage_account when changing account type #110

tombuildsstuff opened this issue Jun 15, 2017 · 1 comment · Fixed by #363

Comments

@tombuildsstuff
Copy link
Contributor

This issue was originally opened by @discordianfish as hashicorp/terraform-provider-azure-classic#27. The original body of the issue is below.


Terraform Version

  • 0.9.8

Affected Resource(s)

  • azurerm_storage_account

Expected Behavior

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

  1. Create a Standard_LRS storage account with terraform and terraform apply
  2. Change the tier to Premium_LRS storage account and terraform apply
tombuildsstuff added a commit that referenced this issue Sep 28, 2017
- 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
@ghost
Copy link

ghost commented Apr 1, 2020

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 ghost locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant