feat: api_key on submit/run for partner (API) node auth#9
Conversation
|
Warning Review limit reached
Next review available in: 33 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (10)
Warning
|
8ff13b8 to
57f5183
Compare
Workflows that use partner/API nodes (Gemini, etc.) authenticate with a single Comfy API key carried in the POST /api/v2/jobs body as extra_data.api_key_comfy_org. submit()/run() (sync and async) gain an optional api_key= parameter that packs it into a typed, closed extra_data object sent alongside the workflow; omit it (or pass "") and no extra_data is sent. - The key never participates in idempotency and is never logged or persisted by the SDK (flows only into the httpx request body). - Shared sans-IO helper keeps sync/async parity; spec + README document the field and disambiguate it from the client-credential api_key. - Adds a CODEOWNERS default owners rule (comfy-cloud-team + core-engine-team), matching the sibling repos. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
57f5183 to
c258bd8
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
What
Workflows that use partner/API nodes (Gemini, etc.) authenticate with a single Comfy API key carried in the
POST /api/v2/jobsbody asextra_data.api_key_comfy_org. This adds an optionalapi_key=parameter tosubmit()/run()(both syncComfyand asyncAsyncComfy) that packs the key into a typed, closedextra_dataobject sent alongside the workflow.api_keyand noextra_datais sent (never an empty object).api_key(which authenticates you to the server); the two are often the same key but conceptually distinct.Tests
New sync + async tests prove
extra_data.api_key_comfy_orgappears as a sibling ofworkflowwhen a key is given, is absent when not, and thatrun()forwards it through.pytest— 34 passed;ruff check,ruff format --check,mypyclean.🤖 Generated with Claude Code