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
permissions, aka sp. This defaults to "r", but should not be applied if "identifier" is passed. It can be worked around via passing permissions: nil. How often are people defining Storage Access Policies with no permission? That said, it's probably not good to foreclose the more obscure use case, so if it is set, it should be respected.
expiry, aka se. This one less ambiguous: it is okay to pass it if the stored access policy is indefinite, and not okay to pass it if it is also defined in the stored access policy. This gem forces you to include it, making Stored Access Policies with expirations unavailable. I removed this line in a local hacked version of the gem, and this got it to work.
The text was updated successfully, but these errors were encountered:
The gem doesn't handle "must be omitted" very well as it comes to using stored access policies.
https://docs.microsoft.com/en-us/rest/api/storageservices/create-service-sas#specifying-the-access-policy
permissions, aka
sp
. This defaults to "r", but should not be applied if "identifier" is passed. It can be worked around via passingpermissions: nil
. How often are people defining Storage Access Policies with no permission? That said, it's probably not good to foreclose the more obscure use case, so if it is set, it should be respected.expiry, aka
se
. This one less ambiguous: it is okay to pass it if the stored access policy is indefinite, and not okay to pass it if it is also defined in the stored access policy. This gem forces you to include it, making Stored Access Policies with expirations unavailable. I removed this line in a local hacked version of the gem, and this got it to work.The text was updated successfully, but these errors were encountered: