feat: add Foundry core transport support - #9510
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). 21 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
125f300 to
c65a148
Compare
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
Why this is needed
Foundry project ownership requires core azd APIs and gRPC transport support so delegated extensions can unset environment values, preserve service configuration updates, and receive structured workflow errors across the process boundary. Without these core contracts, the ownership behavior cannot be implemented reliably by the higher extension layer.
Approach
This layer adds the environment and error protobuf contracts plus generated Go bindings, implements the corresponding gRPC service behavior, preserves step-level workflow flags over inherited globals, and adds structured workflow error unwrapping. The changes stay in core azd transport and service packages so the extension layer can depend on stable APIs rather than duplicating protocol or error handling.
This is the second layer of the PR stack and depends on draft PR #9509 (
hui/foundry-ownership-spec-cda), which contains the Foundry project ownership specification. It intentionally excludes projects, agents, extension manifests, and documentation changes from PR #9508.