Hexalith.Memories.Aspire 2.19.3

Hexalith.Memories.Aspire

The package also exposes AddHexalithMemoriesAccessTelemetry for the fixed lifecycle and independent-clock topology. It is intentionally disabled by default: Story 27.2 supplies portable Dapr boundaries and component templates, while exact Production adapter selection and behavioral certification remain Story 27.3 work.

.NET Aspire hosting extensions for Hexalith.Memories.

A Hexalith domain module that wants to embed the Memories search-index server in its own *.AppHost (for example to make a curated read model searchable) previously had to hand-roll the same wiring: a Redis Stack search/vector container, a FalkorDB graph container, a secret-store component, a conversation/LLM component, the memories project with a DAPR sidecar, and the standard connection-string / topic environment. That boilerplate now lives here.

Usage

using Hexalith.Memories.Aspire;

// stateStore / pubSub are the shared DAPR components the Memories server should reuse
// (for example the ones returned by Hexalith.EventStore.Aspire's AddHexalithEventStore).
HexalithMemoriesSearchIndexServerResources memories = builder.AddHexalithMemoriesSearchIndexServer(
    stateStore,
    pubSub,
    secretStoreComponentPath: secretStoreYamlPath,
    llmComponentPath: llmYamlPath,
    daprPlacementHostAddress: placementAddress,
    daprSchedulerHostAddress: schedulerAddress);

// Apply consumer-specific routing on the returned server resource.
_ = memories.Server
    .WithEnvironment("EventStoreIntegration__Routing__SourceToTenantMap__my-source", "my-index")
    .WithEnvironment("EventStoreIntegration__Routing__AutoProvisionRoutedTenants", "true");

The helper only adds the Memories topology and returns the resource builders; the consuming AppHost owns its DAPR component YAML files and any source-to-index routing.

By default the helper creates a memories-vectors redis/redis-stack container for the Memories search/vector store. Pass redisConnectionString only when the consuming AppHost owns a compatible Redis Stack dependency.

The memories project is referenced cross-repo with IProjectMetadata.SuppressBuild, so the consuming AppHost never compiles it (Aspire runs children with --no-build) and the two repositories' package graphs stay isolated.