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

azurerm_storage_account: crash when importing resource with file encryption enabled #80

Closed
hashibot opened this issue Jun 13, 2017 · 2 comments · Fixed by #363
Closed
Assignees

Comments

@hashibot
Copy link

This issue was originally opened by @lewinski as hashicorp/terraform#14160. It was migrated here as part of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.9.3 (Homebrew)

Affected Resource(s)

  • azurerm_storage_account

Terraform Configuration Files

N/A

Panic Output

https://gist.github.com/lewinski/9cc12d7a6a0698266aebaf50040baf55

Expected Behavior

Terraform should have imported the resource.

Actual Behavior

Terraform crashed.

Steps to Reproduce

  1. Create an Azure Storage account and enable "file" encryption (probably also triggers with queue and table encryption). Example: az storage account create --location="westus" --name="tfbugtestfileenc" --resource-group="tfbugtest" --kind="Storage" --sku="Standard_GRS" --access-tier="Hot" --encryption="file"
  2. Try to import the resource using Terraform: terraform import azurerm_storage_account.importbug /subscriptions/.../resourceGroups/tfbugtest/providers/Microsoft.Storage/storageAccounts/tfbugtestfileenc
  3. Crash.

Important Factoids

Terraform import works fine when 1) no encryption is enabled, or 2) blob encryption is enabled.

The azurerm_storage_account resource does not actually support specifying file, queue, or table encryption. This might be necessary to take care of instead of fixing this issue, because then you could actually use Terraform to correctly manage this setting.

@imcdnzl
Copy link

imcdnzl commented Sep 11, 2017

To clarify the important factoids - you can only specify blob or file, not queue or table against a storage account.

I agree adding file would probably fix this and would be an important thing to add

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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants