aspire-deployment

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying a distributed .NET Aspire application involves 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 you do not hand-write Bicep, Helm charts, Compose files, or CDK stacks. ## Core Features & Use Cases - Target-aware deployment routing: Detects whether the workspace is an Aspire app and routes deployment to Docker Compose, Kubernetes, Azure Container Apps, Azure App Service, Azure Kubernetes Service (AKS), or AWS via aspire publish, aspire deploy, and aspire destroy. - Target-specific reference guides: Loads dedicated references for Azure, AWS, Kubernetes, Docker Compose, JavaScript app serving models, CI/CD pipelines, and preflight checklists only when relevant. - Preflight and safety gates: Inventories parameters, secrets, registries, and cloud credentials before provisioning, and requires explicit confirmation before creating billable resources or running teardown. - Use Case: You have an Aspire AppHost and want to ship it to Azure Container Apps. The Skill adds the integration with aspire add azure-appcontainers, configures the environment resource, previews steps with aspire deploy --list-steps, and deploys with managed identity and ACR wiring handled by Aspire. ## Quick Start Ask the agent to deploy your Aspire app to Azure Container Apps and it will detect the AppHost, configure the target environment, and run the Aspire deploy pipeline.

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, then run aspire deploy. Aspire provisions the environment, builds and pushes images to ACR, and wires managed identity automatically.

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, then run aspire publish -o k8s-artifacts. The output contains Chart.yaml, values.yaml, and templates you can apply with helm install or helm upgrade.

Does Aspire deployment support TypeScript AppHosts?▼

Yes, most targets support TypeScript AppHosts with equivalent APIs such as addAzureContainerAppEnvironment and addKubernetesEnvironment. AWS deployment is currently C#-only, so TypeScript AppHosts cannot use the AWS integration yet.

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

aspire publish generates deployment artifacts like 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.

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. Provide secret values through CI secret stores such as GitHub Actions environment secrets, and run aspire deploy with --non-interactive.

How do I tear down resources created by an Aspire deployment?▼

Run aspire destroy --environment <name> to execute the target's destroy pipeline for the selected AppHost and environment. Confirm the subscription, cluster context, and environment first, and use --yes only when teardown intent is explicit.