Skip to content

Move Foundry remote-tool connection provisioning to Bicep - #27

Draft
Paul Yuknewicz (paulyuk) with Copilot wants to merge 2 commits into
mainfrom
copilot/move-remote-tool-connection-to-bicep
Draft

Paul Yuknewicz (paulyuk) with Copilot wants to merge 2 commits into
mainfrom
copilot/move-remote-tool-connection-to-bicep

Conversation

Copilot AI commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

Move aigw-github from imperative postprovision commands to ARM-managed provisioning, passing the generated gateway key securely across resource groups.

  • Declarative connection: Add a Foundry RemoteTool / CustomKeys connection targeting /default/mcp/github/mcp, ordered after project and gateway-key creation.
  • Secret boundary: Pass runtimeApiKey.listSecrets().key through an @secure() module parameter; emit no key outputs.
  • Hook parity: Remove connection creation from POSIX and PowerShell. Preserve local key storage, GitHub ToolServer registration, model-route readiness, Toolbox creation, and failed-resource recovery.
  • Coverage and docs: Add compiled-template assertions for connection properties, dependencies, secure parameters, and secret-free outputs; document provisioning ownership.

Live preview-key retrieval, fresh/repeated azd up, and Toolbox attachment remain unverified without Azure credentials.

Co-authored-by: paulyuk <1968137+paulyuk@users.noreply.github.com>
Copilot AI changed the title [WIP] Move Foundry remote-tool connection provisioning to Bicep Move Foundry remote-tool connection provisioning to Bicep Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move Foundry remote-tool connection provisioning to Bicep

2 participants