-
Notifications
You must be signed in to change notification settings - Fork 373
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
ci: upload release artifact to supabase s3 bucket #1812
base: master
Are you sure you want to change the base?
Conversation
b411ce3
to
2a2724a
Compare
Pull Request Test Coverage Report for Build 11467779604Details
💛 - Coveralls |
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.
Guessing the secrets have already ben added to Github?
- name: configure aws credentials for uploading release artifacts | ||
uses: aws-actions/configure-aws-credentials@v1 | ||
with: | ||
role-to-assume: ${{ secrets.PROD_AWS_ROLE }} | ||
aws-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.
we only upload the release artifacts when the release-please PR is merged and not the rc versions right? seems like this would push every rc to s3 since the action is also triggered on the release/*
branch
@@ -126,6 +132,8 @@ jobs: | |||
-f "sha=$GITHUB_SHA" | |||
fi | |||
fi | |||
|
|||
aws s3api put-object --bucket ${{ secrets.PROD_ARTIFACTS_BUCKET }} --key auth-v$RELEASE_VERSION-arm64.tar.gz --body ./auth-v$RELEASE_VERSION-arm64.tar.gz |
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.
added PROD_ARTIFACTS_BUCKET
this to the repo secrets
Uploads the release artifact to a Supabase owned S3 bucket for easy releases.