[Bug] Unable to publish KM with Qdrant using Aspire

[v-croft]

Context / Scenario

Hi @dluc.

I found and tried to use your suggestion of how to pick up the API key for a qdrant service created in Aspire:

static string GetConnectionStringPart(IResourceWithConnectionString resource, string pattern)
{
    string? value = resource.ConnectionStringExpression.GetValueAsync(default).Result;
    return value == null ? string.Empty : Regex.Match(value, pattern).Groups.Cast<Group>().Skip(1).FirstOrDefault()?.Value ?? string.Empty;
}

var qdrant = builder.AddQdrant("qdrant");

builder
    .AddProject<Service>("kernel-memory")
    // ...
    .WithReference(qdrant)
    .WithEnvironment("KernelMemory__DataIngestion__MemoryDbTypes__0", "Qdrant")
    .WithEnvironment("KernelMemory__Retrieval__MemoryDbType", "Qdrant")
    .WithEnvironment("KernelMemory__Services__Qdrant__Endpoint",
        () => GetConnectionStringPart(qdrant.Resource, "Endpoint=([^;]+)"))
    .WithEnvironment("KernelMemory__Services__Qdrant__APIKey",
        () => GetConnectionStringPart(qdrant.Resource, "Key=([^;]+)"));

#915 (reply in thread)

What happened?

This worked well on a development machine and KM was able to connect to Qdrant.

However, I trying to create a publish profile for Azure failed with the error:

System.InvalidOperationException: The endpointgrpcis not allocated for the resourceqdrant.

Importance

I cannot use Kernel Memory

Platform, Language, Versions

Current version of KM: 0.95.241216.2
Aspire Version=9.0.0
.NET 9.0
Visual Studio Version 17.12.3

Relevant log output

Partial extract covering failure
      Aspire version: 9.0.0+01ed51919f8df692ececce51048a140615dc759d
fail: Microsoft.Extensions.Hosting.Internal.Host[11]
      Hosting failed to start
      System.InvalidOperationException: The endpoint `grpc` is not allocated for the resource `qdrant`.
         at Aspire.Hosting.ApplicationModel.EndpointReference.get_AllocatedEndpoint() in /_/src/Aspire.Hosting/ApplicationModel/EndpointReference.cs:line 105
         at Aspire.Hosting.ApplicationModel.EndpointReference.get_Url() in /_/src/Aspire.Hosting/ApplicationModel/EndpointReference.cs:line 102
         at Aspire.Hosting.ApplicationModel.EndpointReferenceExpression.GetValueAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/EndpointReference.cs:line 174
         at Aspire.Hosting.ApplicationModel.ReferenceExpression.GetValueAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/ReferenceExpression.cs:line 66
         at Program.<<Main>$>g__GetConnectionStringPart|0_0(IResourceWithConnectionString resource, String pattern) in D:\source\MetricsAnalyzer\DocIndexer.AppHost\Program.cs:line 15

[dluc]

hi @SophisticatedConsulting - it's a known limitation of that approach given Aspire internals, it works only for development.

For Prod, I would recommend using the env vars instead, e.g. using

.WithEnvironment("KernelMemory__Services__Qdrant__Endpoint", "...")
.WithEnvironment("KernelMemory__Services__Qdrant__APIKey", "...")

[v-croft]

Thanks for getting back @dluc but this means that KM essentially is not fully compatible with Aspire.
The value of Aspire is to provide an IaC capability and if we have to manually create services outside of Aspire then this is broken.
With other services I can simply add a reference to Qdrant. using...
.WithReference(qdrant)
so I don't see this as a limitation of Aspire or am I missing something?