aspire-deployment

Orchestrate Aspire AppHost deployment workflows across Docker Compose, Kubernetes, Azure, and AWS.

1|Updated Feb 4, 2025

Search Tags:#deployment #aws #azure #kubernetes #docker #aspire #apphost

Ready to run

npx skills add https://github.com/MarcelMichau/dotnet-starter-project-template --skill aspire-deployment-marcelmichau

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire-deployment
Source: https://github.com/MarcelMichau/dotnet-starter-project-template/tree/main/.agents/skills/aspire-deployment
Command: npx skills add https://github.com/MarcelMichau/dotnet-starter-project-template --skill aspire-deployment-marcelmichau

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, or AWS by orchestrating publish and deploy steps, reducing manual configuration and drift.

Core Features & Use Cases

Unified deployment workflow: coordinates publish artifacts and deployment actions from a single AppHost model across multiple targets.
Target-aware references: automatically loads target-specific guidance (docker/kubernetes/azure/aws) to streamline workflow.
CI/CD friendly: supports non-interactive deploys, parameter/secret handling, and preflight validation for reliable automation.

Quick Start

Run Aspire deploy against your AppHost to publish artifacts and deploy to the selected target.

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 AppHost project to Kubernetes or Azure?▼

You can deploy an Aspire AppHost project by orchestrating publish artifacts and deployment steps across Kubernetes, Azure, AWS, or Docker Compose. The workflow loads target-specific references, validates resources, and applies changes after explicit confirmation.

Can I automate Aspire deployments in a CI/CD pipeline?▼

Yes, Aspire deployments support non-interactive workflows within CI/CD pipelines. The process handles parameters and secrets, runs preflight validation checks, and applies automated pipeline approvals to execute reliable deployments without manual intervention.

What is the best way to manage multiple deployment environments for .NET Aspire apps?▼

Managing multiple Aspire deployment environments involves using a single AppHost model to coordinate target-specific artifact generation. This unified workflow reduces manual configuration drift by validating credentials and applying changes across Docker, Kubernetes, Azure, or AWS.

Does the Aspire deployment workflow support Docker Compose for local testing?▼

Yes, Docker Compose is fully supported as a deployment target. The workflow coordinates publish artifacts and deployment actions for Docker Compose alongside Kubernetes and cloud providers, streamlining local testing from the AppHost model.

What preflight checks are needed before deploying an Aspire app?▼

Aspire deployment preflight checks involve loading target references, validating resources, and verifying credentials before generating artifacts. These checks ensure deployment readiness and prevent errors during non-interactive automated workflows.

Why does my Aspire deployment require explicit confirmation before applying changes?▼

Aspire deployment requires explicit user confirmation or automated pipeline approvals to prevent unintended changes. Following AppHost deployment guidelines, the workflow validates resources and credentials first, applying changes only after approval is granted.