-
SDKs expose
IAzureClientBuilder<EventHubProducerClient, EventHubProducerClientOptions> AddEventHubProducerClient<TBuilder, TConfiguration>(this TBuilder builder, TConfiguration configuration) where TBuilder : IAzureClientFactoryBuilderWithConfiguration<TConfiguration>- Configuration format and binding to options are not defined in Azure SDKs
-
Implementation lives in
Microsoft.Extensions.Azure- binding to options is done by
microsoft.extensions.configurationthroughIConfiguration.Bind()and relies on*Optionsfollowingmicrosoft.extensions.configurationconventions (i.e. properties) - options sources are whatever
microsoft.extensions.configurationsupports:- appsettings.json
- env var config (flat) is supported through ASP.NET Core conventions
- binding to options is done by
-
Configuration options names and structure exactly match Azure SDK (Core, client libs)
*Optionsproperties or reflective constructor parameters and are presumably not strictly consistent- per-client options are hierartical and have base
ClientOptions - credentials are exception and mapping is defined here
- configuration["credential"]
- configuration["clientId"]
- configuration["tenantId"]
- configuration["clientSecret"]
- configuration["clientCertificate"]
- configuration["clientCertificateStoreName"]
- configuration["clientCertificateStoreLocation"]
- per-client options are hierartical and have base
-
There are two layers:
- global (defaults)
- per-client
- it's possible to define options per-client or global
Last active
January 11, 2022 19:31
-
-
Save lmolkova/b35efca6b4745f47d9d82a9c1599a7f6 to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment