Aspire resource support Configuration-based models for configuring resources under well-defined keys. For example, Storage Blob resources support configuration under the Aspire:Azure:Storage:Blobs key.
This configuration model doesn't currently support different configurations for different instances of the same resource type in an application. To address this, we'll update the resource configuration strategy to support instances keyed by name as follows:
At the moment, the primary motivation for doing this is to provide a resolution for the "dual config dilemma" documented in https://github.com/dotnet/aspire/issues/5563 since the existing configuration provider key name scheme doesn't conflict with Azure WebJob's lookup semantics.
Aspire resource support
Configuration
-based models for configuring resources under well-defined keys. For example, Storage Blob resources support configuration under theAspire:Azure:Storage:Blobs
key.This configuration model doesn't currently support different configurations for different instances of the same resource type in an application. To address this, we'll update the resource configuration strategy to support instances keyed by name as follows:
At the moment, the primary motivation for doing this is to provide a resolution for the "dual config dilemma" documented in https://github.com/dotnet/aspire/issues/5563 since the existing configuration provider key name scheme doesn't conflict with Azure WebJob's lookup semantics.
Tracked Integrations