Repository navigation
fix(ci): push the RabbitMQ image to the registry host the workflow logs in to [IFC-3505] - #112
Merged
Merged
Conversation
…gs in to [IFC-3505] The workflow logged in to vars.HARBOR_HOST but pushed to registry.opsmill.io, the host in rabbitmq.image.registry. Docker stores credentials per host, so the push had no credentials and the registry refused it. The push reference now uses vars.HARBOR_HOST with the repository and tag from values.yaml. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fatih-acar
approved these changes
Oct 29, 2026
1 of 2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The manual run of
Build RabbitMQ imageonstabledid not publishregistry.opsmill.io/opsmill/rabbitmq:4.1.3-debian-12-r1-opsmill.1(run 40841269708). The registry answered: "unauthorized to access repository: opsmill/rabbitmq, action: push".The workflow logs in to
vars.HARBOR_HOSTbut pushed to the host inrabbitmq.image.registry,registry.opsmill.io. Docker stores registry credentials per host name, so the push had no credentials. Theinfrahubrepository already pushes its images tovars.HARBOR_HOST(ci-docker-image.yml), and the charts pull them fromregistry.opsmill.io.Jira: IFC-3505. Follows #109.
Changes
vars.HARBOR_HOSTplusrabbitmq.image.repositoryandrabbitmq.image.tagfromcharts/infrahub/values.yaml. The chart still pulls fromregistry.opsmill.io.vars.HARBOR_HOSTis empty, the reference falls back toregistry.opsmill.io, so a build-only run still gets a valid image name.No changelog fragment: only CI configuration changes, which users do not see.
Test plan
yq4.50.1 renders9r2s1098.c1.gra9.container-registry.ovh.net/opsmill/rabbitmq:4.1.3-debian-12-r1-opsmill.1with this expression and the currentvalues.yaml.yamllintandactionlintpass on the workflow.pushonstablepublishes the image, anddocker buildx imagetools inspect registry.opsmill.io/opsmill/rabbitmq:4.1.3-debian-12-r1-opsmill.1finds it.stablepass.🤖 Generated with Claude Code