Add public ECR push to release workflow - #352
Merged
Merged
Conversation
Publishes rotel to public.ecr.aws/rotel-dev/rotel alongside DockerHub on release. Uses OIDC to assume the AWS IAM role stored in AWS_ECR_PUBLIC_ROLE_ARN secret.
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
1 participant
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
docker-push-rotel-ecrjob to the release workflow, running in parallel with the existing DockerHub pushpublic.ecr.aws/rotel-dev/rotelon each releaseAWS_ECR_PUBLIC_ROLE_ARNsecret — no long-lived AWS credentials requiredSetup required
Add the GitHub Actions secret
AWS_ECR_PUBLIC_ROLE_ARNto therotel-dev/rotelrepo with the ARN of the IAM role created by therotel-public-ecrTerraform stack (github-actions-rotel-dev-rotel-ecr-public-repo).