aspire-deployment

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

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

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 integrations 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 and AppHost model instead of ad-hoc cloud tooling, preventing misconfigured deployments and fragmented infrastructure workflows. ## 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 add, aspire publish, aspire deploy, and aspire destroy. - Preflight and preview validation: Inventories parameters, secrets, registries, and cloud settings, then lists pipeline steps with aspire publish --list-steps or aspire deploy --list-steps before any billable resources are created. - CI/CD automation guidance: Provides GitHub Actions workflow patterns for C# and TypeScript AppHosts, including Azure OIDC login, Parameters__* environment variable mapping, and non-interactive deploy/destroy jobs. - Use Case: A developer with an Aspire AppHost containing a web frontend, API, and Redis cache asks to deploy to Azure Container Apps. The Skill adds the azure-appcontainers integration, configures the environment resource, validates Azure subscription settings, previews the deployment steps, and runs aspire deploy. ## Quick Start Deploy my Aspire app to Azure Container Apps using the AppHost in this repository.

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. Configure Azure__SubscriptionId, Azure__Location, and Azure__ResourceGroup as environment variables before deploying.

How do I deploy an Aspire app to Kubernetes?

Run aspire add kubernetes and add a Kubernetes environment resource to the AppHost. For existing clusters, configure a container registry and verify kubectl context; aspire deploy then builds images and installs Helm charts into the cluster.

What is the difference between aspire publish and aspire deploy?

aspire publish generates deployment artifacts such as docker-compose.yaml, 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 I deploy an Aspire app to AWS?

Yes, via aspire add aws, which uses the AWS Aspire integrations to map resources to CDK constructs and CloudFormation. The AWS path is preview, C# AppHost-only, and requires AWS credentials, CDK bootstrap, and Node.js 22.x.

How do I run aspire deploy in GitHub Actions CI/CD?

Install the Aspire CLI in the workflow, set up the .NET or Node toolchain, authenticate with azure/login or cloud credentials, and pass AppHost parameters as Parameters__* environment variables. Run aspire deploy with --non-interactive and gate it with a GitHub Environment.

How do I tear down resources created by aspire deploy?

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