Name and Version
0.21.0
What is the problem this feature will solve?
Extend Deployment and Upstream configuration to support interface-specific settings and forwarding modes.
The following configuration fields should be supported:
Deployment
- defaultHeaders — default HTTP headers for requests to the deployment.
- baseUrl — base URL of the deployment endpoint.
DeploymentInterface
- defaultHeaders — interface-specific default HTTP headers.
- mode — interface forwarding mode: PASSTHROUGH or TRANSLATION. If absent, PASSTHROUGH must be used for backward compatibility.
- features — interface-specific feature flags overriding deployment-level features. The effective configuration is merged field by field. If features is absent, deployment-level features are inherited. An explicitly empty reasoningEfforts array clears the inherited list.
Upstream
- baseUrl — root URL used when an interface does not define its own endpoint.
- interfaces — interface-specific configuration for:
openaiChatCompletions
openaiResponses
anthropicMessages
openaiEmbeddings
Each interface may override endpoint, key, extraData, and secretExtraData using the new UpstreamInterface definition.
What is the feature you are proposing to solve the problem?
What alternatives have you considered?
Name and Version
0.21.0
What is the problem this feature will solve?
Extend Deployment and Upstream configuration to support interface-specific settings and forwarding modes.
The following configuration fields should be supported:
Deployment
DeploymentInterface
Upstream
openaiChatCompletions
openaiResponses
anthropicMessages
openaiEmbeddings
Each interface may override endpoint, key, extraData, and secretExtraData using the new UpstreamInterface definition.
What is the feature you are proposing to solve the problem?
What alternatives have you considered?