aspire-configuration

Configure .NET Aspire AppHost to map resource outputs to environment variables.

57|7|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/seiggy/lucia-dotnet --skill aspire-configuration-seiggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-configuration
Source: https://github.com/seiggy/lucia-dotnet/tree/main/.github/skills/aspire-configuration
Command: npx skills add https://github.com/seiggy/lucia-dotnet --skill aspire-configuration-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing configuration in .NET Aspire applications, ensuring that application code remains clean and decoupled from Aspire's infrastructure concerns, promoting portability and transparency.

Core Features & Use Cases

  • Explicit Configuration Mapping: Translates Aspire resource outputs into explicit environment variables for application consumption.
  • Decoupled Application Code: Prevents application projects from depending on Aspire client or service-discovery packages.
  • Production Parity: Ensures that configuration injected by AppHost can be easily mirrored in production environments using standard methods like environment variables.
  • Use Case: When developing a .NET Aspire application, use this Skill to ensure your API project only consumes configuration via IOptions<T> and doesn't directly interact with Aspire's service discovery mechanisms, making it easier to deploy and test.

Quick Start

Use the aspire-configuration skill to wire AppHost resources to application configuration in Aspire-based repos.

Frequently Asked Questions about aspire-configuration

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

FAQPage Schema
How do I decouple application code from .NET Aspire service discovery?

You can decouple application code by configuring the AppHost to emit explicit environment variables that map resource outputs directly to IOptions<T> bindings, eliminating app project dependencies on Aspire client packages.

What is the best way to manage .NET Aspire AppHost configuration for production parity?

The best way to achieve production parity in .NET Aspire AppHost configuration is translating resource outputs into standard environment variables, ensuring configuration transparency and portability across staging and production environments.

How do I pass Aspire resource outputs to application configuration via environment variables?

You pass Aspire resource outputs by wiring the AppHost to emit explicit environment variables from those outputs, allowing the application to consume configuration cleanly through standard IOptions<T> pattern bindings.

Can I use IOptions<T> bindings instead of Aspire clients in my microservices application?

Yes, you can use IOptions<T> bindings instead of Aspire clients by configuring the AppHost to map resource outputs to environment variables, keeping microservices application code decoupled from infrastructure concerns and highly portable.

Why should I configure .NET Aspire AppHost to emit explicit environment variables?

You should configure .NET Aspire AppHost to emit explicit environment variables to ensure production configuration transparency and portability, allowing standard deployment methods to mirror local AppHost configuration injection without specialized service discovery mechanisms.

Does aspire-configuration support mapping resource outputs without Aspire client packages?

Yes, this Skill supports mapping Aspire AppHost resource outputs to explicit environment variables without requiring Aspire client or service-discovery packages in the application project, facilitating clean application code and decoupled service discovery.