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 Shared Access Signatures for Azure Files service #90

Closed
hashibot opened this issue Jun 13, 2017 · 4 comments
Closed

Support Shared Access Signatures for Azure Files service #90

hashibot opened this issue Jun 13, 2017 · 4 comments

Comments

@hashibot
Copy link

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


Hi there,

Terraform Version

Terraform v0.9.4

Affected Resource(s)

azurerm_storage_share

Expected Behavior

Please support a way to create Shared Storage Signatures for the storage_share resources.

These are authentication keys that offer greater granularity on the access that can be granted on a file share. For example one can create a SAS for the file share alone and offer this access to an enduser, without needing the storage account key that by itself can offer access to too many resources and cannot basically be shared at all. SAS on the other hand can be applied on a file share alone, can have a TTL, one can create multiple SAS and basically are a better way to provide limited access to the file resource.

Actual Behavior

there is no "azure_storage_signature" provider

Important Factoids

links to example code that creates SAS
https://docs.microsoft.com/en-us/azure/storage/storage-dotnet-shared-access-signature-part-2
https://github.com/Azure/azure-storage-python/blob/master/azure/storage/file/fileservice.py

@gehridav
Copy link

gehridav commented Dec 1, 2017

We are exactly looking for that feature, would be great to have this in soon!

@anoff
Copy link

anoff commented Apr 30, 2018

Might be clone of #59 and solved by this PR #1011

@tombuildsstuff
Copy link
Contributor

@anoff agreed - this is a duplicate of #59 / will be fixed by #1011 - closing in favour of #59

@ghost
Copy link

ghost commented Mar 31, 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 Mar 31, 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

5 participants