Stavanger Brass Band avatar

Stavanger Brass Band

Official

@Stavanger-Brass-Band · Norway

0Followers
|
2Public Repos
|
4Published Skills

Microsoft-authored Aspire 13.4 skills for deploying, orchestrating, and monitoring distributed .NET cloud-native apps across Docker, Kubernetes, Azure, and AWS.

Skills Distribution
DomainCloud & Comp...Cloud-Native Deplo.. (35%)Distributed App Or.. (30%)Observability & Te.. (25%)Developer Tooling .. (10%)

Agent Skills by Stavanger Brass Band

Showing 4 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Stavanger Brass Band

FAQPage Schema
What tasks can I perform with the Aspire skill set?▼

You can deploy Aspire AppHost apps to Docker Compose, Kubernetes, Azure, or AWS; manage app lifecycle with start, stop, wait, and restart; recover from file locks and port conflicts; and observe logs, traces, metrics, and resource state via the Aspire dashboard, App Insights, and AKS diagnostics.

Who should use these Aspire skills?▼

.NET engineers and platform teams building cloud-native distributed applications with Aspire 13.4 AppHosts. They suit developers running aspire CLI commands, publishing container artifacts, and operators diagnosing deployed workloads on Azure Container Apps or AKS clusters.

How do the Aspire skills route and execute at runtime?▼

The top-level aspire skill detects the AppHost, enforces safety guardrails, and routes to sub-skills: aspire-orchestration for lifecycle, aspire-deployment for publish/teardown, and aspire-monitoring for telemetry. Single operations invoke the aspire CLI or target cloud CLIs directly.

What license and cost apply to these Aspire skills?▼

All four skills are released under the MIT license by Microsoft, version 0.0.1, making them free to use, modify, and redistribute. Underlying cloud resources on Azure or AWS incur their own standard provider charges.

What prerequisites do the Aspire skills require?▼

A repository containing an Aspire AppHost is required; non-Aspire .NET projects, container-only repos, and Azure provisioning without Aspire are explicitly out of scope. Runtime depends on the aspire CLI plus target environment CLIs such as Docker, kubectl, or Azure tooling.