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
This would remove the 5GB artifact size limit we currently have. This would need to be implemented as a flag during upload, e.g. meta.multipart, because the process is entirely different than when using a singular presigned upload URL. Artifact-related jobs would also need to be adjusted.
@andrewgoodchild apologies if I was unclear, though on my end presigned multipart uploads are working. The gist you mentioned was me sharing with trevor how I had previously coded the authorization header before getting presigned multipart uploads working.
This is my new version of the (ruby) code that works for getting presigned urls for both single and multipart uploads. Hopefully seeing this will give you ideas for how to solve it similarly in your code:
Notice how the first parameter of the presigned_url method is different between single and multipart uploads, and that multipart uploads take the regular key (filename) just like single part uploads, but also add parameters for setting the upload_id and part_number.
This would remove the 5GB artifact size limit we currently have. This would need to be implemented as a flag during upload, e.g.
meta.multipart
, because the process is entirely different than when using a singular presigned upload URL. Artifact-related jobs would also need to be adjusted.Originally posted by @dnewkerk in aws/aws-sdk-js#468 (comment):
Ref keygen-sh/keygen-cli#6.
The text was updated successfully, but these errors were encountered: