We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Based on the updates to config for 2.1 adding chained config, we can move the 2.x Azure Key Vault config provider topic samples (sample 1, sample 2) to a nicer config setup ...
WebHost.CreateDefaultBuilder(args) .ConfigureAppConfiguration((context, config) => { var builtConfig = config.Build(); var keyVaultConfigBuilder = new ConfigurationBuilder(); keyVaultConfigBuilder.AddAzureKeyVault( $"https://{builtConfig["Vault"]}.vault.azure.net/", builtConfig["ClientId"], builtConfig["ClientSecret"]; config.AddConfiguration(keyVaultConfigBuilder); }) .Build()
@scottaddie Can you create a label for 2.1 for this? ... or mark it blocked right now?
2.1
blocked
The text was updated successfully, but these errors were encountered:
@guardrex Label created and applied
Sorry, something went wrong.
Make sure this is updated to the latest version without tabs from previous versions. If you need previous versions, point to https://github.com/aspnet/Docs/blob/master/aspnetcore/common/_static/9-25-17.pdf
This is revised: Keep the 1.x samp, update the 2.0 samp to 2.1.
guardrex
No branches or pull requests
Based on the updates to config for 2.1 adding chained config, we can move the 2.x Azure Key Vault config provider topic samples (sample 1, sample 2) to a nicer config setup ...
@scottaddie Can you create a label for
2.1
for this? ... or mark itblocked
right now?The text was updated successfully, but these errors were encountered: