You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
With the aws-ecr-push-image pipe it would be really useful to be able to pass the Registry ID (AWS Account ID) as a parameter. This is required when the user belongs to a different AWS account than the registry it is pushing to.
@Dave McDermid Has this been implemented yet ?
Would a registry id be needed to even push to a public registry within the same account, in my case I am getting the following error and during build the repository is being searched under private only and not public
"The repository with name 'xxxxxxxx' does not exist in the registry with id 'xxxxxxxxx'"
This hasn't been implemented yet, either implement this or please add support for AWS STS Assume Role rather than go overboard with OIDC. Some of us have our runners in AWS and would like to keep them separate from the devs while still giving them visibility into the registry for things like container image scan results.
Either an STS assume role of specifying the account ID rather than access keys or simply specifying the AWS account Id and combining that with a Resource Policy on the ECR repo itself.