aspire-deployment

Deploy Aspire AppHost applications to Docker Compose, Kubernetes, Azure, or AWS.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill aspire-deployment-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire-deployment
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.agents/skills/aspire-deployment
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill aspire-deployment-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying a distributed Aspire application to production requires choosing a target platform, wiring the right hosting integration into the AppHost, resolving parameters and secrets, and running the correct publish/deploy/destroy pipeline. This Skill routes all of that through the Aspire CLI so deployments stay AppHost-native instead of drifting into hand-edited Bicep, Helm, or Compose files. ## Core Features & Use Cases - Target-aware deployment routing: Detects whether the workspace is an Aspire app and routes deployment work to Docker Compose, Kubernetes, Azure Container Apps, Azure App Service, Azure Kubernetes Service (AKS), or AWS references. - Aspire-native publish, deploy, and destroy: Drives aspire publish, aspire deploy, aspire destroy, and aspire do <step> with preflight checks for parameters, secrets, registries, and cloud credentials. - CI/CD automation guidance: Provides GitHub Actions workflow patterns for validating, publishing, and deploying Aspire apps with OIDC Azure login and environment-gated production deploys. - Use Case: A user asks to deploy their Aspire app to Azure Container Apps. The Skill detects the AppHost, runs aspire add azure-appcontainers, adds the environment resource, preflights subscription and parameters, previews with aspire deploy --list-steps, and deploys with aspire deploy. ## Quick Start Ask the assistant to deploy your Aspire app to a chosen target, for example: deploy this Aspire application to Azure Container Apps.

Frequently Asked Questions about aspire-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an Aspire app to Azure Container Apps?▼

Run aspire add azure-appcontainers, add an Azure Container Apps environment resource to the AppHost, mark public workloads with WithExternalHttpEndpoints, then run aspire deploy. Configure Azure__SubscriptionId, Azure__Location, and Azure__ResourceGroup before deploying.

How do I generate Kubernetes or Helm artifacts from an Aspire AppHost?▼

Add the Kubernetes hosting integration with aspire add kubernetes, add a Kubernetes environment resource and a container registry, then run aspire publish -o k8s-artifacts. The output includes Chart.yaml, values.yaml, and templates you can inspect or apply with Helm.

What is the difference between aspire publish and aspire deploy?▼

aspire publish generates deployment artifacts such as Compose files, Helm charts, or CDK output for review or handoff. aspire deploy resolves parameters and applies the deployment directly from the AppHost model; it does not consume a previously published output directory.

Can Aspire deploy to AWS with a TypeScript AppHost?▼

No. The AWS deployment integration is currently a C# AppHost-only preview driven by the AWS Aspire integrations repository and CDK. TypeScript AppHosts are not supported for the AWS deployment path.

How do I pass secrets and parameters to aspire deploy in CI?▼

Map AppHost parameters to environment variables using the Parameters__name convention, replacing dashes with underscores, and supply them from CI secret stores such as GitHub Environment secrets. Run aspire deploy with --non-interactive so prompts do not stall the pipeline.

When should I not use this Aspire deployment workflow?▼

Do not use it when the workspace has no Aspire AppHost; in that case initialize one first or use generic Azure, Kubernetes, Docker, or AWS tooling. It also does not manage externally-created clusters or registries outside the Aspire deployment target.