fix(api-keys): mint real control-plane keys, not local ones#14
Conversation
Dashboard API-key creation wrote to a local table, so the keys never
authenticated against the CP/engine (they looked created but didn't
work). Proxy to the CP's real endpoints instead:
POST/GET/DELETE /admin/v1/orgs/{orgId}/api-keys via the session. Now a
created key is a genuine CP key that works against the API.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
Warning Review limit reached
Next review available in: 46 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
1 participant
Dashboard API-key creation wrote to a local table, so keys never authenticated against the CP/engine — they appeared created but didn't work. Now proxies to the CP's real endpoints (
POST/GET/DELETE /admin/v1/orgs/{orgId}/api-keys) via the session, so a created key is a genuine, working CP key.