You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the orb does not use the --registry-id parameter and defaults to the account id of the current account. We use a technical user that accesses the registry of a different account. The orb does not support this, so we had to manually run the aws ecr commands the orb uses internally, passing the --registry-id parameter.
Why is this needed
This will allow working with a different account than the one the registry is contained in.
The text was updated successfully, but these errors were encountered:
What would you like to be added
Currently the orb does not use the --registry-id parameter and defaults to the account id of the current account. We use a technical user that accesses the registry of a different account. The orb does not support this, so we had to manually run the aws ecr commands the orb uses internally, passing the --registry-id parameter.
Why is this needed
This will allow working with a different account than the one the registry is contained in.
The text was updated successfully, but these errors were encountered: