aspire-configuration

Emit explicit environment variables from Aspire AppHost to services.

Updated Apr 23, 2026

Search Tags:#configuration #configuration management #environment variables #aspire #apphost

Ready to run

npx skills add https://github.com/MudraMartin/dotlight-skillset --skill aspire-configuration-mudramartin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire-configuration
Source: https://github.com/MudraMartin/dotlight-skillset/tree/main/dotnet/aspire-configuration
Command: npx skills add https://github.com/MudraMartin/dotlight-skillset --skill aspire-configuration-mudramartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps to streamline the process of wiring configuration between an Aspire AppHost and its services, ensuring production configuration transparency and portability without the need for Aspire client/service-discovery packages in application code.

Core Features & Use Cases

Configuration Wiring: Simplifies the configuration process for Aspire applications, allowing for explicit environment variable and configuration key management.
Avoiding Service Discovery: Keeps Aspire client/service-discovery packages out of application code, enhancing maintainability.
Feature Toggles: Enables feature toggles for development and testing environments that match production settings.

Quick Start

Set up Aspire configuration in your project using this skill. Configure AppHost to emit explicit environment variables, and bind your application to these variables using IOptions<T> or Configuration.

Frequently Asked Questions about aspire-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I wire configuration between Aspire AppHost and services without service discovery packages?▼

To wire Aspire AppHost configuration without service discovery packages, configure the AppHost to emit explicit environment variables. Bind your application code directly to these variables using IOptions<T> or Configuration to ensure production configuration transparency.

What is the best way to manage Aspire environment variables for production portability?▼

The best way to manage Aspire environment variables for portability is emitting them explicitly from the AppHost. This approach avoids Aspire client packages in application code, ensuring transparent configuration that matches development, testing, and production settings.

How do I set up feature toggles in Aspire that match production configuration?▼

To set up Aspire feature toggles matching production, use explicit environment variable configuration wiring. This enables feature toggles for development and testing environments that accurately reflect production settings without relying on service-discovery packages.

Why should I avoid Aspire client and service-discovery packages in my application code?▼

Avoiding Aspire client and service-discovery packages in application code enhances maintainability and production configuration transparency. Relying on explicit environment variables instead ensures your application remains portable and decoupled from specific infrastructure packages.

Can I use IOptions<T> to bind Aspire AppHost environment variables in my application?▼

Yes, you can use IOptions<T> to bind Aspire AppHost environment variables in your application. The AppHost emits explicit environment variables, and your application reads them using IOptions<T> or Configuration patterns for transparent wiring.