Aspire Community Toolkit

The Aspire Community Toolkit provides a collection of community-created integrations and extensions for .NET Aspire. These packages are generally categorized into two types:

1. Hosting Integrations: Used in the Aspire AppHost to provision and run resources like databases, message brokers, or runtimes (e.g., Hosting.Golang, Hosting.PostgreSQL.Extensions, Hosting.Ollama).
2. Client Integrations: Used in your application code to provide seamless connection and configuration for the hosted resources (e.g., OllamaSharp, Meilisearch, MinIO.Client).

Some packages provide extensions for existing core Aspire integrations to add specialized functionality (e.g., Hosting.Redis.Extensions, Hosting.MongoDB.Extensions).

The Aspire Community Toolkit provides a wide range of hosting and client integrations for .NET Aspire. These integrations allow you to easily orchestrate and connect to various runtimes, databases, messaging systems, and cloud services within your Aspire application.

Common categories of integrations include:

• Runtimes & Languages: Golang, Java, Node.js, Python, Rust, Deno, Bun, Perl.
• Databases & Storage: SQLite, PostgreSQL, SQL Server, MySQL, MongoDB, Meilisearch, SurrealDB, RavenDB, Minio, KurrentDB, Elasticsearch.
• Messaging & Streaming: ActiveMQ, LavinMQ, Redis.
• Cloud & Infrastructure: Azure Extensions, Dapr, K3s, Kind, Bitwarden Secret Manager.
• Developer Tools: MailPit, k6, Flagd, GoFeatureFlag, SQL Database Projects.

There are two ways to route telemetry from your projects to the OpenTelemetry Collector:

1. Manual Redirection: Use .WithOpenTelemetryCollectorRouting(collector) on specific projects or resources. Only the resources explicitly called will forward their telemetry to the collector.
2. Automatic Redirection: Call .WithAppForwarding() on the collector instance. This automatically forwards telemetry for all projects and resources that have the OtlpExporterAnnotation applied.

// Manual approach
builder.AddProject<Projects.MyApi>("api")
    .WithOpenTelemetryCollectorRouting(collector);

// Automatic approach
var collector = builder.AddOpenTelemetryCollector("collector")
    .WithConfig("./config.yaml")
    .WithAppForwarding();

builder.AddProject<Projects.MyApi>("api");

When a component requests a secret value via IValueProvider.GetValueAsync, the BitwardenSecretResource follows a specific priority order to ensure the authoritative remote state is used:

1. Bitwarden resolved-secret cache: This is the highest priority. It is populated during the sync phases (Phase 2/2.5) or during provisioning. It represents the actual state in Bitwarden.
2. Managed Secrets Fallback: For managed secrets, if the cache is empty, the resource falls back to the ParameterResource mechanism (waiting for values provided via configuration or user input). This serves as the "write path" for new secrets.
3. Reference-only Fallback: For reference-only secrets, if the Bitwarden cache is empty (which typically only happens before Phase 2.5 completes), it returns null.

The [AspireExport] attribute is used to register types and methods with the Aspire Type System (ATS). This allows them to be called from polyglot apphosts (such as TypeScript or Python) via the JSON-RPC remote host.

• Resource Types: Carry [AspireExport] to register their type IDs.
• Extension Methods: Methods like AddBitwardenSecretManager, GetSecret, AddSecret, and WithReference carry [AspireExport] to define the polyglot API surface.
• Exclusions: C# ergonomics overloads or methods with ATS-incompatible parameters (like EndpointReference or generic callback types) are marked with [AspireExportIgnore] to explicitly prevent them from being exported.

Breakage Signal: If the ASPIREATS001 diagnostic stops compiling, the export mechanism has changed.

During a local run, the BitwardenSecretResource follows a state machine to manage authentication and parameter collection. Understanding these states helps in debugging provisioning delays or failures.

Important: To ensure your application starts only after Bitwarden is ready, you must explicitly call .WaitForCompletion(bitwarden) in your AppHost code for any dependent resources.