[skip-changelog] use OIDC to retrieve the credentials #2541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
- [ ] Tests for the changes have been added (for bug fixes / features)- [ ] Docs have been added / updated (for bug fixes / features)- [ ]UPGRADING.md
has been updated with a migration guide (for breaking changes)- [ ]configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
infra change
What is the current behavior?
We currently use statically generated credentials to access to s3 buckets.
What is the new behavior?
OpenID Connect allows workflows to exchange short-lived tokens directly from your cloud provider (see here)
Does this PR introduce a breaking change, and is titled accordingly?
no
Other information
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
from secretsAWS_ROLE_TO_ASSUME
to secrets