Repository navigation
chore: migrate openchoreo container registry - #675
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (8)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request changes Helm chart references and container image repository hosts from ChangesRegistry Reference Updates
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to The registry-reference changes are mergeable with normal checks. The available evidence does not identify a broken image reference. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Signed-off-by: chathuranga95 <siriwardhanachathuranga@gmail.com>
0378acb to
2c9979e
Compare
Purpose
This PR migrates the container registry used for fetching openchoreo system components and default community modules managed by openchoreo
Related issues
openchoreo/openchoreo#4899
Approach
Refactor
ghcr.io/openchoreoregistry tocr.openchoreo.devand update installation guides.Checklist
Summary by CodeRabbit
cr.openchoreo.dev.cr.openchoreo.dev.