revert: use AWS access keys instead of OIDC role #3137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Revert to using the AWS access keys for the Prod ECR push workflow as the OIDC roles will not exist until the Prod infrastructure release. Once the infrastructure release has gone through, this can be switched back to using OIDC roles.
craigzour
approved these changes
Jan 23, 2024
🧪 Review environmenthttps://bayxot2b77agluitjpj3qjdqxe0ddcsm.lambda-url.ca-central-1.on.aws/ |
bryan-robitaille
approved these changes
Jan 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Revert to using the AWS access keys for the Prod ECR push workflow as the OIDC roles will not exist
until the Prod infrastructure release.
Once the infrastructure release has gone through, this can be switched back to using OIDC roles.
Related