-
Notifications
You must be signed in to change notification settings - Fork 50
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
Re-implement signedBlobReadUrl with a getAccountSAS call #259
Re-implement signedBlobReadUrl with a getAccountSAS call #259
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Do you know if this changes the format of the code URL? If so, that will cause Functions to be updated when this is adopted to point to the new URL (pointing to the same code). I think that's okay - but curious whether that's what we expect to happen or not.
Yes, it will, the URL will be different. Both parameter order and values are different. Note that we are using a SAS on a different level - account not a specific blob. Fine-grained SAS tokens aren't supported. This puts us into a worse position security-wise. Should be fine for accounts auto-created inside our Serverless code, but doesn't feel great anyway. |
@@ -40,8 +40,8 @@ export function signedBlobReadUrl(blob: Blob | ZipBlob, account: Account): pulum | |||
const signatureExpiration = "2100-01-01"; | |||
|
|||
return pulumi.all([account.name, account.primaryConnectionString, blob.storageContainerName, blob.name]).apply( | |||
([accountName, connectionString, containerName, blobName]) => | |||
getAccountSAS({ | |||
async ([accountName, connectionString, containerName, blobName]) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
Thanks much! |
Fixes #258