-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix: mc fails on uploading large files to gcs #25
Conversation
63f7aca
to
33467a6
Compare
917bd55
to
314343b
Compare
mc cp --recursive /backups/output/ remote/"$STORAGE_BUCKET_NAME" | ||
AWS_ACCESS_KEY_ID=$STORAGE_ACCESS_KEY \ | ||
AWS_SECRET_ACCESS_KEY=$STORAGE_SECRET_KEY \ | ||
AWS_DEFAULT_REGION=us-east-1 \ |
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.
This is here so that boto
does not bail. It does not have any effect.
@@ -1,5 +1,7 @@ | |||
#!/bin/bash | |||
|
|||
set -e | |||
mc alias set remote "$STORAGE_ENDPOINT" "$STORAGE_ACCESS_KEY" "$STORAGE_SECRET_KEY" --api "$STORAGE_SIGNATURE_VERSION" | |||
mc cp --recursive /backups/output/ remote/"$STORAGE_BUCKET_NAME" | |||
AWS_ACCESS_KEY_ID=$STORAGE_ACCESS_KEY \ |
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.
This mapping of env vars is here so that:
a. we don't need chart changes
b. people could get confused about how we now need AWS credentials
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.
I gotta say from an ops perspective I feel a bit uneasy about not just using the google client, but implementation wise this looks fine to me, so approved ✔️
mc
fails uploading larger files (> 12GB) to GCS. This PR moves the upload to use AWS CLI instead.AWS CLI is Apache-2.0 licensed, so packaging it here shall be fine.