feat(plugin): support plugin-defined roles#3113
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 ignored due to path filters (1)
📒 Files selected for processing (10)
✨ 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 |
f0d6335 to
810bf06
Compare
071012d to
8e9dbd7
Compare
Expose plugin roles from the invocation token to both gRPC and HTTP operation handlers. This lets plugin authors inspect assigned roles through InvokeCtx or HTTP context helpers while Mission Control continues to enforce only operation invocation permissions.
8e9dbd7 to
a644b4b
Compare
Plugins can now declare roles in their manifest and Mission Control resolves matching
plugin-role:<plugin>:<role>permissions during invocation.Mission Control still only enforces
invoke:<plugin>:<operation>for access, then forwards any resolved roles in the short-lived invocation JWT.The plugin SDK exposes those roles to gRPC and HTTP operation handlers so plugins can apply their own role-aware authorization.