azd up uses launchSettings.json

[mizrael]

It seems that when deploying with Aspire using azd up, the CLI uses the environment variables defined in the launchSettings.json file from the Aspire Host's Properties folder. Is that the expected behavior?

I thought that file was used only when running the solution locally.

I have some env vars defined in the selected environment folder under .azure/, but they get replaced.

[mizrael]

quick update: looks like the CLI is picking the first profile available in launchSettings.json.

My workaround so far is to add a "deploy" profile at the very beginning, without any env var. When running locally from VS, I will be using the other one instead.

{
  "$schema": "https://json.schemastore.org/launchsettings.json",
  "profiles": {
    "deploy": { // this is the profile that will be used by the CLI when deploying the app
      "commandName": "Project",
      "dotnetRunMessages": true,
      "launchBrowser": true,
      "applicationUrl": "https://localhost:17282;http://localhost:15253",
      "environmentVariables": {
      }
    },
   "https": {
      "commandName": "Project",
      "dotnetRunMessages": true,
      "launchBrowser": true,
      "applicationUrl": "https://localhost:17282;http://localhost:15253",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      }
    }
}

[SteveHSX7]

Hey - I've just been seeing the same issue where "azd up" is picking up the first profile which has the environment set to "Development" which was causing some hiccups down the line.

This link (admittedly a little older) :

#1189

Also implies the build will be a Debug build which doesn't seem right either - it does look like I only have "Debug" build folders on my dev machine, are you seeing the same?

[mizrael]

same for me too

[SteveHSX7]

I can find quite a few mentions of this, e.g Azure/azure-dev#3436 and #5178 but no out and out fixes?

[SteveHSX7]

Actually looking more closely I think it might be building Release. The "AppHost" project isn't build as an assembly in the "azd up" context - it's just used to create the manifest. My individual projects do have a bin/Release/net9.0/linux-x64 folder (which will be for the the container as I develop on Windows / Mac so isn't for my local development) :