-
-
Notifications
You must be signed in to change notification settings - Fork 150
[skip-changelog] use OIDC to retrieve the credentials #901
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
Conversation
- name: configure aws credentials | ||
uses: aws-actions/configure-aws-credentials@v4 | ||
with: | ||
role-to-assume: ${{ secrets.AWS_ROLE_TO_ASSUME }} |
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 has been added to the environment production
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} | ||
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_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.
- TODO remove these from the secrets
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
TODO remove AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from secrets TODO add AWS_ROLE_TO_ASSUME to secrets
* followup of #901, fix CI * fix permissions * fix environment * set permissions for the entire workflow * replace create-release deprecated action with the same one used in the cli * do not configure credentials when in pre-release (they are not used)
Please check if the PR fulfills these requirements
before creating one)
- [ ] Tests for the changes have been added (for bug fixes / features)Infra change
We currently use statically generated credentials to access to s3 buckets.
OpenID Connect allows workflows to exchange short-lived tokens directly from your cloud provider (see here)
Nop