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: add support for kind (Storage/BlobStorage) and access tier (Hot/Cool) #8558

Closed
nicocesar opened this issue Aug 30, 2016 · 3 comments

Comments

@nicocesar
Copy link

nicocesar commented Aug 30, 2016

Terraform Version

terraform 0.7.2

Affected Resource(s)

azurerm_storage_account

Expected Behavior

Terraform should support

  • the account kind (Storage/BlobStorage)
  • the access tier for Blob storage accounts (Hot/Cool)

Note: this is different from SKU Name (LRS/ZRS/GRS/RAGRS/PLRS) which terraform already supports

Actual Behavior

It supports SKU name via "type" attribute (note that azure added "kind" which isn't "type", yes, I know it confusing)

Steps to Reproduce

You can see this in the azure CLI:

$ azure --version
0.10.3 (node: 0.10.40)
$ azure storage account create --help
help:    Create a storage account
help:    
help:    Usage: storage account create [options] <name>
(..)
help:      --sku-name <skuName>                                   the SKU name (LRS/ZRS/GRS/RAGRS/PLRS)
help:      --kind <kind>                                          the account kind (Storage/BlobStorage)
help:      --access-tier <accessTier>                             the access tier for Blob storage accounts (Hot/Cool)
(..)
help:    Current Mode: arm (Azure Resource Management)

References

https://msdn.microsoft.com/en-us/library/azure/microsoft.azure.management.storage.models.storageaccount.accesstier.aspx

@nicocesar
Copy link
Author

Any updates on this?

@stack72
Copy link
Contributor

stack72 commented Oct 31, 2016

Added via #9408

@stack72 stack72 closed this as completed Oct 31, 2016
@ghost
Copy link

ghost commented Apr 20, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants