fix(registry): update mission-control plugin release assets#41
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR updates the plugin registry configuration in ChangesPlugin Registry Configuration Migration
Possibly Related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
Mission Control plugins now publish multiple plugin artifacts under conventional shared release tags instead of per-plugin tags or Go module installs. Update the postgres and kubernetes-logs deps registry entries to resolve GitHub release assets, select the new extracted plugin binary names, and use the shared release checksum file.
70da7e6 to
38e3c1f
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pkg/config/defaults.yaml`:
- Line 84: The binary_path value in pkg/config/defaults.yaml is incorrect:
change the kubernetes_logs_mc_plugin entry to kubernetes-logs_mc_plugin so the
configured binary name matches the packaged artifact; update the binary_path key
value (in the defaults.yaml entry `binary_path`) to the hyphenated name to
ensure correct binary selection after extraction.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 88062775-93d3-4c14-878a-93bf0d438522
📒 Files selected for processing (1)
pkg/config/defaults.yaml
Mission Control plugins now ship under conventional shared release tags like
v1.0.1, with per-plugin assets in the same release.Update the deps registry entries for
postgres-mc-pluginandkubernetes-logs-mc-pluginto use GitHub release assets, shared checksum files, and the new extracted plugin binary names.Summary by CodeRabbit