aspire-configuration

Convert Aspire resource outputs into explicit environment variables and configuration keys.

Updated Feb 10, 2026

Search Tags:#production #configuration #environment-variables #service-discovery #aspire #apphost #explicit-mapping

Ready to run

npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill aspire-configuration-tientt010

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire-configuration
Source: https://github.com/tientt010/Dotnet-JiraLite-Microservices/tree/main/.github/skills/aspire-configuration
Command: npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill aspire-configuration-tientt010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure Aspire AppHost to translate resource outputs into explicit app configuration keys that are visible in production, keeping application code free of Aspire clients and service discovery.

Core Features & Use Cases

Explicit mapping of Aspire resource outputs to environment variables and config keys, enabling apps to bind via IOptions<T> or Configuration without referencing Aspire packages.
Production parity and portability by ensuring every injected value can be represented as env vars or config files outside of Aspire, and supporting feature toggles for dev/test.
AppHost-centric approach that confines Aspire hosting and service-discovery concerns to the AppHost, preventing Aspire clients from leaking into application projects.

Quick Start

Configure Aspire AppHost to translate resources into explicit environment variables that your app reads.

Frequently Asked Questions about aspire-configuration

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

FAQPage Schema

How do I configure Aspire AppHost to use environment variables instead of service discovery?▼

You map Aspire resource outputs to explicit environment variables in the AppHost, keeping application code free of Aspire clients while enabling IOptions<T> binding without service discovery packages.

Why do I need explicit mapping for Aspire resource outputs in production?▼

Explicit mapping guarantees production parity by ensuring every Aspire-injected value can be reproduced as standard environment variables or config entries outside of Aspire.

Can I use IOptions<T> to bind configuration without referencing Aspire packages in my application?▼

Yes, by translating resource outputs into explicit environment variables in the AppHost, your application can bind configuration via IOptions<T> without referencing Aspire packages directly.

Does configuring explicit environment variables in Aspire support feature toggles for dev and test?▼

Yes, explicit environment variable mapping supports feature toggles for dev and test by allowing configuration overrides without altering application code, while maintaining production parity.

What are the limitations of using explicit app config via environment variables in Aspire?▼

A limitation is that it requires explicit AppHost mapping for every resource output, meaning you must manually wire each value to a configuration key rather than relying on automatic Aspire service discovery.