azd init fails after upgrading to Preview 5 #3780

nickna · 2024-04-17T19:36:11Z

nickna
Apr 17, 2024

I have an Aspire project (based on the Aspire labs) that I refactored to Preview 5.

When I type azd init in the solution root, it traverses my solution hierarchy, finds the AppHost project, then starts building.

azd init builds a manifest in %TEMP%, which doesn't persist after it fails. AppHost appears to have a well-formed JSON manifest when I manually generate a manifest with dotnet run --project MyProj.AppHost.csproj --publisher manifest --output-path apphost-manifest.json

What am I doing wrong?
Any help would be greatly appreciated.

AZD output:

C:\Code\MyProj>azd init --debug
2024/04/16 23:48:00 main.go:59: azd version: 1.8.0 (commit 8246323c2472148288be4b3cbc3c424bd046b985)
2024/04/16 23:48:00 main.go:229: using cached latest version: 1.8.0 (expires on: 2024-04-18T03:55:58Z)
2024/04/16 23:48:00 middleware.go:106: running middleware 'debug'
2024/04/16 23:48:00 middleware.go:106: running middleware 'experimentation'
2024/04/16 23:48:00 experimentation.go:42: assignment context: 0g5ad841:76970;
2024/04/16 23:48:00 middleware.go:106: running middleware 'telemetry'
2024/04/16 23:48:00 telemetry.go:38: TraceID: 2685651e1446ca0ecda5cb46cfce73e2
2024/04/16 23:48:00 command_runner.go:307: Run exec: 'git --version' , exit code: 0
-------------------------------------stdout-------------------------------------------
git version 2.39.2.windows.1
2024/04/16 23:48:00 git.go:72: git version: git version 2.39.2.windows.1

Initializing an app to run on Azure (azd init)

? How do you want to initialize your app? Use code in the current directory

  |       | Scanning app code in current directory2024/04/16 23:48:05 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj

2024/04/16 23:48:05 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\MyProj.AppHost
  |==     | Scanning app code in current directory2024/04/16 23:48:06 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\MyProj.AppHost\MyProj.AppHost.csproj --getProperty:IsAspireHost' , exit code: 0
2024/04/16 23:48:06 appdetect.go:267: Found project dotnet-apphost at C:\Code\MyProj\MyProj.AppHost
2024/04/16 23:48:06 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\MyProj.ServiceDefaults
  |=====  | Scanning app code in current directory2024/04/16 23:48:06 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\MyProj.ServiceDefaults\MyProj.ServiceDefaults.csproj --getProperty:IsAspireHost' , exit code: 0
2024/04/16 23:48:06 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Api
  |=======| Scanning app code in current directory2024/04/16 23:48:07 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\Api\MyProj.Api.csproj --getProperty:IsAspireHost' , exit code: 0
  |   ====| Scanning app code in current directory2024/04/16 23:48:07 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\Api\MyProj.Api.csproj --getProperty:RuntimeIdentifier' , exit code: 0
2024/04/16 23:48:07 appdetect.go:267: Found project dotnet at C:\Code\MyProj\Api
2024/04/16 23:48:07 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Api.Db
  |      =| Scanning app code in current directory2024/04/16 23:48:08 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\Api.Db\Core.Db.csproj --getProperty:IsAspireHost' , exit code: 0
2024/04/16 23:48:08 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Api.Db\DB Init
2024/04/16 23:48:08 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Api.Db\Models
2024/04/16 23:48:08 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Api.Db\Models\Email
2024/04/16 23:48:08 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Api.Db\Models\ServiceInfo
2024/04/16 23:48:08 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Api.Db\Models\User Accounts
2024/04/16 23:48:08 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Core.Db.Manager
  |=      | Scanning app code in current directory2024/04/16 23:48:08 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\Core.Db.Manager\Core.Db.Manager.csproj --getProperty:IsAspireHost' , exit code: 0
  |====   | Scanning app code in current directory2024/04/16 23:48:09 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\Core.Db.Manager\Core.Db.Manager.csproj --getProperty:RuntimeIdentifier' , exit code: 0
2024/04/16 23:48:09 appdetect.go:267: Found project dotnet at C:\Code\MyProj\Core.Db.Manager
2024/04/16 23:48:09 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Keycloak
2024/04/16 23:48:09 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Keycloak\data
2024/04/16 23:48:09 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Keycloak\data\import
2024/04/16 23:48:09 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Shared
2024/04/16 23:48:09 appdetect.go:259: Detecting projects in directory: C:\Code\MyProj\Web
  |=======| Scanning app code in current directory2024/04/16 23:48:10 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\Web\Web.csproj --getProperty:IsAspireHost' , exit code: 0
  |   ====| Scanning app code in current directory2024/04/16 23:48:10 command_runner.go:307: Run exec: 'dotnet msbuild C:\Code\MyProj\Web\Web.csproj --getProperty:RuntimeIdentifier' , exit code: 0
2024/04/16 23:48:10 appdetect.go:267: Found project dotnet at C:\Code\MyProj\Web
  |     ==| Scanning app code in current directory2024/04/16 23:48:13 command_runner.go:307: Run exec: 'dotnet run --project MyProj.AppHost.csproj --publisher manifest --output-path C:\Users\nickn\AppData\Local\Temp\azd-provision61996858\apphost-manifest.json' , exit code: 0
-------------------------------------stdout-------------------------------------------
Building...
info: Aspire.Hosting.DistributedApplication[0]
      Aspire version: 8.0.0-preview.5.24201.12+1b627b7d5d399d4f9118366e7611e11e56de4554
info: Aspire.Hosting.Publishing.ManifestPublisher[0]
      Published manifest to: C:\Users\nickn\AppData\Local\Temp\azd-provision61996858\apphost-manifest.json

ERROR: failed to generate manifest from app host project: unmarshalling manifest: unexpected end of JSON input

Here's the manifest output that I manually generated:

{
  "resources": {
    "db": {
      "type": "container.v0",
      "connectionString": "Host={db.bindings.tcp.host};Port={db.bindings.tcp.port};Username=postgres;Password={postgrespassword.value}",
      "image": "postgres:16.2",
      "volumes": [
        {
          "name": "MyProj.AppHost-db-data",
          "target": "/var/lib/postgresql/data",
          "readOnly": false
        }
      ],
      "env": {
        "POSTGRES_HOST_AUTH_METHOD": "scram-sha-256",
        "POSTGRES_INITDB_ARGS": "--auth-host=scram-sha-256 --auth-local=scram-sha-256",
        "POSTGRES_USER": "postgres",
        "POSTGRES_PASSWORD": "{postgrespassword.value}"
      },
      "bindings": {
        "tcp": {
          "scheme": "tcp",
          "protocol": "tcp",
          "transport": "tcp",
          "targetPort": 5432
        }
      }
    },
    "MyProj": {
      "type": "value.v0",
      "connectionString": "{db.connectionString};Database=MyProj"
    },
    "idp": {
      "type": "container.v0",
      "image": "quay.io/keycloak/keycloak:24.0.2",
      "args": [
        "start-dev",
        "--import-realm"
      ],
      "bindMounts": [
        {
          "source": "../Keycloak/data/import",
          "target": "/opt/keycloak/data/import",
          "readOnly": false
        }
      ],
      "env": {},
      "api": {
        "type": "project.v0",
        "path": "../Api/MyProj.Api.csproj",
        "env": {
          "OTEL_DOTNET_EXPERIMENTAL_OTLP_EMIT_EXCEPTION_LOG_ATTRIBUTES": "true",
          "OTEL_DOTNET_EXPERIMENTAL_OTLP_EMIT_EVENT_LOG_ATTRIBUTES": "true",
          "ASPNETCORE_FORWARDEDHEADERS_ENABLED": "true",
          "ConnectionStrings__MyProj": "{MyProj.connectionString}",
          "services__idp__http__0": "{idp.bindings.http.url}"
        },
        "bindings": {
          "http": {
            "scheme": "http",
            "protocol": "tcp",
            "transport": "http"
          },
          "https": {
            "scheme": "https",
            "protocol": "tcp",
            "transport": "http"
          }
        }
      },
      "webapp": {
        "type": "project.v0",
        "path": "../Web/Web.csproj",
        "env": {
          "OTEL_DOTNET_EXPERIMENTAL_OTLP_EMIT_EXCEPTION_LOG_ATTRIBUTES": "true",
          "OTEL_DOTNET_EXPERIMENTAL_OTLP_EMIT_EVENT_LOG_ATTRIBUTES": "true",
          "ASPNETCORE_FORWARDEDHEADERS_ENABLED": "true",
          "services__idp__http__0": "{idp.bindings.http.url}",
          "services__api__http__0": "{api.bindings.http.url}",
          "services__api__https__0": "{api.bindings.https.url}"
        },
        "bindings": {
          "http": {
            "scheme": "http",
            "protocol": "tcp",
            "transport": "http",
            "external": true
          },
          "https": {
            "scheme": "https",
            "protocol": "tcp",
            "transport": "http",
            "external": true
          }
        }
      },
      "postgrespassword": {
        "type": "parameter.v0",
        "value": "{postgrespassword.inputs.value}",
        "inputs": {
          "value": {
            "type": "string",
            "secret": true,
            "default": {
              "generate": {
                "minLength": 22
              }
            }
          }
        }
      }
    }
  }

Answered by vhvb1989

Apr 18, 2024

Discovered this issue recently when doing something else.
Will create a fix soon. The issue is within the withOrder[T] component we added to keep the bindings order :)
It fails in some cases when there are no bindings (null)

View full answer

davidfowl · 2024-04-18T05:19:46Z

davidfowl
Apr 18, 2024
Maintainer

Very odd @ellismg @vhvb1989

5 replies

vhvb1989 Apr 18, 2024

Discovered this issue recently when doing something else.
Will create a fix soon. The issue is within the withOrder[T] component we added to keep the bindings order :)
It fails in some cases when there are no bindings (null)

Answer selected by nickna

vhvb1989 Apr 18, 2024

Azure/azure-dev#3743

vhvb1989 Apr 19, 2024

@nickna , As I was trying to fix this, I noticed that the JSON you shared is not valid.

See how the api service is nested within the idp service in the manifest:

Is this maybe a copy/paste issue? or is that actually what dotnet is generating?
Can you share the code from your AppHost program that generates such manifest? That would be a bug for Aspire generating the manifest @davidfowl @mitchdenny

vhvb1989 Apr 19, 2024

Another interesting fact is that idp has no bindings node, which would break the reference from a project to it:

davidfowl Apr 19, 2024
Maintainer

Can we get the application @nickna ?

nickna · 2024-04-19T19:13:44Z

nickna
Apr 19, 2024
Author

Certainly.
I pushed my project to this public Github repo

4 replies

vhvb1989 Apr 19, 2024

Thanks. It looks an issue to the extension KeycloakContainerResource to me. Here: https://github.com/nickna/SampleDotNetAspireProj/blob/master/AppHost/KeyCloakResource.cs#L24

The extension API has an issue producing valid manifest. You might want to take a look to it.

nickna Apr 19, 2024
Author

Thanks for investigating!

This extension method was initially published as a code sample for Preview 3.

Minor changes were needed because of revisions in Aspire Preview 4:

WithHttpEndpoint() parameter name changes
Migration of WithVolumeMount() to WithBindMount().

davidfowl Apr 21, 2024
Maintainer

@mitchdenny can you take a look?

mitchdenny Apr 21, 2024
Collaborator

In the KeyCloakResource you need to await WriteContainerAsync. I've created a PR for the code sample you linked:

MicrosoftDocs/mslearn-aspire-starter#7

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

azd init fails after upgrading to Preview 5 #3780

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 9 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

azd init fails after upgrading to Preview 5 #3780

nickna Apr 17, 2024

Replies: 2 comments · 9 replies

davidfowl Apr 18, 2024 Maintainer

vhvb1989 Apr 18, 2024

vhvb1989 Apr 18, 2024

vhvb1989 Apr 19, 2024

vhvb1989 Apr 19, 2024

davidfowl Apr 19, 2024 Maintainer

nickna Apr 19, 2024 Author

vhvb1989 Apr 19, 2024

nickna Apr 19, 2024 Author

davidfowl Apr 21, 2024 Maintainer

mitchdenny Apr 21, 2024 Collaborator

nickna
Apr 17, 2024

Replies: 2 comments 9 replies

davidfowl
Apr 18, 2024
Maintainer

davidfowl Apr 19, 2024
Maintainer

nickna
Apr 19, 2024
Author

nickna Apr 19, 2024
Author

davidfowl Apr 21, 2024
Maintainer

mitchdenny Apr 21, 2024
Collaborator