Aspire first release scoping

Below are the set of features and scenarios in scope for the first Aspire release (built on .NET 8.0).

Aspire Resources and Components

OSS

• Postgres, MySql, SQLServer, Oracle, Mongo, Redis, Kafka, RabbitMQ

Azure

• Cosmos, Storage (Queues, Tables, Blobs), Service Bus, KeyVault, Open AI, AI Search, Azure Redis, Azure Postgres, Azure SQL

Dapr

• State Store, PubSub

Dashboard

• The aspire dashboard decoupling so it can be deployed in any environment
• Native support for the aspire dashboard support in ACA

Deployment

• Making sure all supported azure resources and open-source resources can be deployed to azure via AZD
• Command line CI/CD scaffolding for github actions and azdo via AZD
• First class support for Azure Monitor when deployed to ACA
• Kubernetes Support provided by the community via aspirate (thank you @prom3theu5)

Tooling

• VS deployment experience driven by azd
• VS code experience for Aspire
• VS CI/DI scaffolding for for github actions and azdo powered by AZD

Top requested end to end scenarios (dev to deploy)

• (p1) Scenario: Ability to connect to a remote azure resource from development #1758
• (p1) Ability to set dotnet user-secrets during dev time from AZD-set envvars (related: Provide a way to write select bicep outputs to dotnet user-secrets for Aspire apps Azure/azure-dev#3202)
• (p2) Ability to customize azure resources as part of deployment. Our plan B on this is that we already have support for doing this via azd infra synth.
• Support for podman/docker in WSL
• Developing against a container locally and deploying using ACA addons
• Developing against a container locally and deploying using an already provisioned resource
• Developing against a container locally and deploying a managed azure resource
• Ability to add azure resources not natively supported by aspire as part of deployment
• Ability to deploy the aspire dashboard into production
• Ability to send telemetry to Azure Monitor when deployed to ACA
• Ability to use aspire orchestration with multiple repositories

Out of scope

• AWS Support (in discussion, there are various prototypes)
• Local Stack support (need to figure out how AWS and local stack are exposed)
• GCP Support
• AKS support (will work via aspirate tool)
• Azure Functions