You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix interceptor contract inconsistency for start_update_with_start_workflow (#1588)
* Fix interceptor contract inconsistency for start_update_with_start_workflow
Add top-level rpc_metadata and rpc_timeout fields to
StartWorkflowUpdateWithStartInput, making it consistent with every other
OutboundInterceptor input dataclass. Previously this composite input
lacked these fields, forcing interceptors to special-case it.
Also fix the _ClientImpl to actually pass rpc_metadata and rpc_timeout
to the execute_multi_operation gRPC call, which were previously silently
dropped.
Add a test verifying that rpc_metadata set by an interceptor on
StartWorkflowUpdateWithStartInput is forwarded to the gRPC call.
Fixes#1582
* Remove unused rpc_metadata/rpc_timeout from child interceptor inputs
Remove rpc_metadata and rpc_timeout fields from
UpdateWithStartUpdateWorkflowInput and UpdateWithStartStartWorkflowInput.
These fields were never forwarded to the underlying execute_multi_operation
gRPC call — only the top-level StartWorkflowUpdateWithStartInput fields
are authoritative.
Also remove the corresponding parameters from WithStartWorkflowOperation
since they only served to populate the (now-removed) child input fields.
This is a breaking change for interceptors that accessed rpc_metadata or
rpc_timeout on the child input objects.
0 commit comments