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
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.
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 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 31, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: