Skip to content

chore: rename OCI_REGISTRY_USERNAME to PUSH_OCI_REGISTRY#247

Merged
wallyworld merged 1 commit intojuju:mainfrom
wallyworld:rename-ociregistry-var
Apr 27, 2026
Merged

chore: rename OCI_REGISTRY_USERNAME to PUSH_OCI_REGISTRY#247
wallyworld merged 1 commit intojuju:mainfrom
wallyworld:rename-ociregistry-var

Conversation

@wallyworld
Copy link
Copy Markdown
Member

Juju now uses PUSH_OCI_REGISTRY so update the jujud operator build to use it instead of OCI_REGISTRY_USERNAME

Copy link
Copy Markdown
Member

@jack-w-shaw jack-w-shaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Soz I didn't get around to submitting this myself last week!

This will break 4.0 and main builds atm, but I don't mind because the referenced change will be landing in 4.0 and main imminently

@jack-w-shaw
Copy link
Copy Markdown
Member

Also a question - how does juju in our CI know to pull from the jujuqabot ecr registry?

@wallyworld wallyworld merged commit 153b037 into juju:main Apr 27, 2026
2 checks passed
@wallyworld
Copy link
Copy Markdown
Member Author

Also a question - how does juju in our CI know to pull from the jujuqabot ecr registry?

See select-oci-registry job - it uses a OPERATOR_IMAGE_ACCOUNT env var, which is used by main.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants