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
presignUrls for public files might be useful for handing over write or delete permissions, obviously read is not useful.
we do not support it for now but still don't throw an error, and the user receives a non working presign URL
@purplecabbage yes, it's about generating the presign URL against the public container instead of the private one when the file starts with 'public/' prefix
This needs fixing in two places:
Expected Behaviour
presignUrls for public files might be useful for handing over write or delete permissions, obviously read is not useful.
we do not support it for now but still don't throw an error, and the user receives a non working presign URL
Actual Behaviour
via TVM credentials:
init
write('public/hello', 'world')
generatePresignURL('public/hello', { expiryInSeconds: 60, permissions: 'rwd' })
Reason for failure: TVM will generate against the private container: https://github.com/adobe/aio-tvm/blob/master/lib/impl/AzurePresignTvm.js#L51
via BYO credentials:
write('public/hello', 'world')
generatePresignURL('public/hello', { expiryInSeconds: 60, permissions: 'rwd' })
Reason for failure: same points to private container in all cases https://github.com/adobe/aio-lib-files/blob/master/lib/impl/AzureBlobFiles.js#L551
The text was updated successfully, but these errors were encountered: