From aecc13ee479dadec62551b8fbe4fb7af683134da Mon Sep 17 00:00:00 2001 From: Martin Fletcher Date: Fri, 24 May 2024 11:08:06 +0100 Subject: [PATCH] Update aca-deployment-azd-in-depth.md - Add missing dotnet cli command argument Missing '--output-path' parameter from dotnet cli command under point 1 of 'How Azure Developer CLI integration works' section --- docs/deployment/azure/aca-deployment-azd-in-depth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment/azure/aca-deployment-azd-in-depth.md b/docs/deployment/azure/aca-deployment-azd-in-depth.md index 13d5e06677..ce6472c469 100644 --- a/docs/deployment/azure/aca-deployment-azd-in-depth.md +++ b/docs/deployment/azure/aca-deployment-azd-in-depth.md @@ -45,7 +45,7 @@ The `azd init` workflow provides customized supported for .NET Aspire projects. :::image type="content" source="media/azd-internals.png" alt-text="Illustration of internal processing of `azd` when deploying .NET Aspire application."::: -1. When `azd` targets a .NET Aspire application it starts the AppHost with a special command (`dotnet run --project AppHost.csproj -- --publisher manifest`), which produces the Aspire [manifest file](../manifest-format.md). +1. When `azd` targets a .NET Aspire application it starts the AppHost with a special command (`dotnet run --project AppHost.csproj --output-path manifest.json --publisher manifest`), which produces the Aspire [manifest file](../manifest-format.md). 1. The manifest file is interrogated by the `azd provision` sub-command logic to generate Bicep files in-memory only (by default). 1. After generating the Bicep files, a deployment is triggered using Azure's ARM APIs targeting the subscription and resource group provided earlier. 1. Once the underlying Azure resources are configured, the `azd deploy` sub-command logic is executed which uses the same Aspire manifest file.