#19338 Allow multiple registry configurations with the same address Issue created by bobthemighty Is your feature request related to a problem? Please describe. I am pushing images to a central AWS account, the registry address is the same for all repositories in the account: $ACCOUNT_ID.dkr.ecr.eu-west-1.amazonaws.com. I have some repositories that engineers can push to directly, and others that limit writes to the CI principals. For example, I have a docker image that we use as an environment for some build steps. I would like to build this image in CI and make it available to engineers, but they should not be able to push new versions. Describe the solution you'd like I would like to have two registry configurations, one exclusively for CI and one for tinkering, pointing to the same address. That allows me to mark some repositories as

skip_push

in pants.toml, but enable push from pants.ci.toml Describe alternatives you've considered I can just mark each image as skip_push and then push them manually from the CI host, but it's ungainly. I could set up a DNS name for the protected registry so that they're disambiguated. I'm probably going to add a tag to the targets that should only run on CI and disable them in pants.toml Additional context There's a repo here showing the problem, from what I can tell, the addresses collide because they're used to match the registry with tags here in the publish goal. pantsbuild/pants