.NET: Expose Executor Binding Metadata from Workflows #3389
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
As part of adding Durable support for workflows, we need access to executor binding metadata so that the Durable orchestration workflow runner can correctly route messages at runtime. The runner itself will be introduced in a follow-up PR from the corresponding feature branch.
Additional Context
The Python implementation already exposes executor binding information, whereas the .NET implementation does not. This PR closes that gap and brings feature parity between the two.
Description
This PR exposes executor binding information from a workflow, similar to the existing APIs that expose ports and edges.
This method allows callers to retrieve a copy of the executor bindings defined in a workflow.
Contribution Checklist