I am running the cluster in us-west-2 and I set the registry variable to us-east-2, where our primary registry exists. This is a common practice. The region in the requirements file is set to us-west-2. When a build runs the container push fails because the region is set to us-west-2 and cannot authenticate with us-east-2. I updated the jx-requirements.yaml file and push the change to our repo. The build job runs and overrites the registry value, and checks it back in. The value is not updated, but is overwritten.
Problem
I am running the cluster in us-west-2 and I set the registry variable to us-east-2, where our primary registry exists. This is a common practice. The region in the requirements file is set to us-west-2. When a build runs the container push fails because the region is set to us-west-2 and cannot authenticate with us-east-2. I updated the jx-requirements.yaml file and push the change to our repo. The build job runs and overrites the registry value, and checks it back in. The value is not updated, but is overwritten.
Requirements YAML
JX Version
I am not using a custom versionStream.
Workaround
I am setting the .jx/secrets file in a code repository to the us-west registry and it works fine.
TLDR;
I cannot change the registry value in a previously installed system.