Skip to content

chore: sync vendored Comfy Router spec (cloud@5a3b668) #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
comfy-pr-bot wants to merge 1 commit into from
+4 −4
Closed

chore: sync vendored Comfy Router spec (cloud@5a3b668) #148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions spec/router-openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -346,7 +346,7 @@ components:
additionalProperties: true
RouterModelSegment:
type: string
description: Lowercase `model` segment of the canonical `{provider}/{model}[/{variant}]` model ID - the model to run within that provider. Shared by the invocation route's `model` path parameter and a catalog entry's `model` field, for the same no-drift reason as `RouterProviderSegment`.
description: Lowercase `model` segment of the canonical `{provider}/{model}` model ID - the model to run within that provider. Shared by the invocation route's `model` path parameter and a catalog entry's `model` field, for the same no-drift reason as `RouterProviderSegment`.
pattern: ^[a-z0-9]+([._-][a-z0-9]+)*$
maxLength: 128
example: flux-2-pro
Expand All @@ -359,7 +359,7 @@ components:
example: q7Fm2xTn9pLd4RsV
RouterProviderSegment:
type: string
description: Lowercase `provider` segment of the canonical `{provider}/{model}[/{variant}]` model ID - the partner whose model is being addressed. The invocation route's `provider` path parameter and a catalog entry's `provider` field both reference this one schema, which is what keeps the listed IDs and the accepted IDs from drifting apart.
description: Lowercase `provider` segment of the canonical `{provider}/{model}` model ID - the partner whose model is being addressed. The invocation route's `provider` path parameter and a catalog entry's `provider` field both reference this one schema, which is what keeps the listed IDs and the accepted IDs from drifting apart.
pattern: ^[a-z0-9]+([._-][a-z0-9]+)*$
maxLength: 64
example: bfl
Expand Down Expand Up @@ -518,14 +518,14 @@ components:
name: model
in: path
required: true
description: Lowercase model segment of the canonical `{provider}/{model}[/{variant}]` model ID - the model to run within that provider.
description: Lowercase model segment of the canonical `{provider}/{model}` model ID - the model to run within that provider.
schema:
$ref: '#/components/schemas/RouterModelSegment'
RouterProvider:
name: provider
in: path
required: true
description: Lowercase provider segment of the canonical `{provider}/{model}[/{variant}]` model ID - the partner whose model is being run.
description: Lowercase provider segment of the canonical `{provider}/{model}` model ID - the partner whose model is being run.
schema:
$ref: '#/components/schemas/RouterProviderSegment'
headers:
Expand Down
Loading