Use role-based authentication to push images#43
Merged
Conversation
harsh-gulhane
approved these changes
May 26, 2026
This file contains hidden or 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
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.
This PR updates all workflows in this projects to use role-based authentication instead of access key pair to authenticate with public ECR repository.
We want to move to role-based authentication as it's more secured than using access key pair. The previous access key pair has been revoked.
Because this is a public repository, the
PUBLIC_ECR_ROLEandAWS_REGIONhas been set via repository secrets.I've confirmed that this is working:
Note that this PR also modernize the way we build and push image by using actions instead of calling
dockerdirectly.