vikingowl
8d1c839093
Group A — gap fills: - restore Client.GetWorkflowWorkerInfo (regression from v1.3.0; /v1/workflows/workers/whoami is still in the spec and is needed by callers running custom workers) - add Client.GetChatCompletionFields, GetChatCompletionFieldOptions, GetChatCompletionFieldOptionsCounts (previously-missing observability fields API) Group B — Python SDK v2.3.0..v2.4.3 sync: - workflow.EncodedPayloadOption typed enum (offloaded / encrypted / encrypted-partial); replaces []string on NetworkEncodedInput.EncodingOptions. Wire-compatible refinement; source-incompatible for callers that built the slice as []string literals. - workflow-connector integration: ConnectorSlot, ConnectorBindings, ConnectorExtensions, WorkflowExtensions, BuildConnectorExtensions(...) helper, ConnectorAuthTaskState, ConnectorAuthStatus constants. New Extensions map[string]any field on workflow.ExecutionRequest. - HITL confirmation constants: conversation.Confirmation enum (ConfirmationAllow/Deny) and ConfirmationStatusPending/Allowed/Denied alongside the pre-existing ToolCallConfirmation type and tool_confirmations field. No-op verification: - ChatCompletionChoice.message remains singular per spec v1.0.0; Python's 'messages[]' rename was internal SDK shape, not wire format. Tests: 297 (was 284), all green. go vet clean.
13 lines
446 B
Go
13 lines
446 B
Go
package workflow
|
|
|
|
// WorkerInfo describes the worker scheduler the SDK is connected to.
|
|
//
|
|
// Returned by GET /v1/workflows/workers/whoami. Useful when running custom
|
|
// workers that need to know which scheduler / namespace to connect to.
|
|
// For managed deployments, prefer Registration.DeploymentID.
|
|
type WorkerInfo struct {
|
|
SchedulerURL string `json:"scheduler_url"`
|
|
Namespace string `json:"namespace"`
|
|
TLS bool `json:"tls"`
|
|
}
|