skills.rest
Stavanger-Brass-Band
Stavanger-Brass-BandOFFICIAL
Explore all skills by this author →
GitHub

aspire-deployment

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

Updated Jan 20, 2021
Search Tags:#ci/cd#deployment#azure#github actions#kubernetes#docker compose#aspire
One-click install
npx skills add https://github.com/Stavanger-Brass-Band/sheetmusic-api --skill aspire-deployment-stavanger-brass-band
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire-deployment
Source: https://github.com/Stavanger-Brass-Band/sheetmusic-api/tree/main/.agents/skills/aspire-deployment
Command: npx skills add https://github.com/Stavanger-Brass-Band/sheetmusic-api --skill aspire-deployment-stavanger-brass-band

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying a .NET Aspire application involves choosing a target platform, configuring the AppHost deployment environment, resolving parameters and secrets, and running the right publish or deploy pipeline. This Skill routes all of that through the Aspire CLI so deployment stays AppHost-native instead of hand-editing Bicep, Helm, or Compose files. ## Core Features & Use Cases - Target-aware deployment routing: Detects existing AppHost deployment environments and guides target selection across Docker Compose, Kubernetes, Azure Container Apps, Azure App Service, Azure Kubernetes Service (AKS), and AWS. - Preflight and preview: Inventories parameters, secrets, and compute-environment assignments, then runs aspire publish --list-steps or aspire deploy --list-steps before any resources are provisioned. - CI/CD automation: Provides GitHub Actions workflow patterns for publishing artifacts, pushing container images, deploying with OIDC Azure login, and gated teardown via aspire destroy. - Use Case: You have an Aspire AppHost and want to ship it to Azure Container Apps from GitHub Actions. The Skill adds the Azure target integration, configures subscription and resource group settings, and generates a workflow that runs aspire deploy --environment Production --non-interactive. ## Quick Start Ask the assistant to deploy your Aspire app to Azure Container Apps and it will inspect the AppHost, add the target integration, preflight parameters, 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`. Configure Azure__SubscriptionId, Azure__Location, and Azure__ResourceGroup as environment variables on the deploy process.

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

aspire publish generates target artifacts such as Compose files, Helm charts, or Bicep 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 Kubernetes or AWS?▼

Yes. Use `aspire add kubernetes` for Helm-based Kubernetes deployment or `aspire add aws` for deployment through the AWS Aspire integrations and CDK. Both follow the same publish, deploy, and destroy pipeline as other targets.

How do I pass secrets to aspire deploy in GitHub Actions?▼

Map AppHost parameters to environment variables using the Parameters__name convention, sourcing values from GitHub Environment secrets. Parameter names with dashes use underscores, for example registry-endpoint becomes Parameters__registry_endpoint.

Why does aspire deploy prompt during CI runs?▼

Some targets emit deploy-time selection prompts that are not AppHost parameters, such as Azure tenant selection. Make the login context unambiguous with az login --tenant or azure/login tenant-id, and pass --non-interactive only after values are configured.

When should I not use Aspire-native deployment?▼

Aspire deployment requires an AppHost in the workspace. If no AppHost exists, initialize one first; for non-Aspire projects, use generic Azure, Kubernetes, Docker, or AWS deployment tooling instead.

Related Skills

Explore More Software Engineering Skills→
withakaywithakay

aspireify

Automate Aspire AppHost initialization and wiring for existing applications.

Community
Advanced
davisdredavisdre
9

azure-diagnostics

Diagnose Azure production issues across Container Apps, Function Apps, and AKS using systematic checks and KQL queries.

Community
Intermediate
dodygdodyg

dotnet-aspire-patterns

Orchestrates .NET Aspire AppHost topology, service discovery, health checks, and OpenTelemetry defaults for local dev and testing.

Community
Advanced
ecoDriverltdecoDriverltd

aspire-deployment

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

Official
Advanced