Switch to upstream blazar - #2558
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (3)
🔇 Additional comments (2)
📝 WalkthroughSwitches from the StackHPC Blazar fork to upstream Blazar. Removes the fork source definition and adds the WalkthroughThe change pins Kolla and Kolla-Ansible to StackHPC release tags, removes the Blazar source override, and adds a Rocky 10 Blazar image tag. ChangesKolla configuration updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The PR switches to upstream Blazar and updates Kolla pins and image tagging behavior in localized configuration; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.) 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 |
c3ae377 to
4a828cc
Compare
Switches to upstream blazar instead of our stackhpc fork.
Also bumps our kolla/kolla-ansible pins and switches back to using tags. This should let them auto-update with our weekly syncs again