History

Aaron Crawfis eb568116e5 SDK Docs (#572 ) * Setup dapr docs content * Update SDK docs for new format * Update daprdocs/content/en/dotnet-sdk-contributing/dotnet-contributing.md Co-authored-by: Ryan Nowak <nowakra@gmail.com> * Update daprdocs/content/en/dotnet-sdk-contributing/dotnet-contributing.md Co-authored-by: Ryan Nowak <nowakra@gmail.com> * Update python reference * Update samples to examples * Update layout * Update prereqs * Apply correct branding for .NET Core vs .NET * Update examples/Client/StateManagement/README.md * fix solution file Co-authored-by: Ryan Nowak <nowakra@gmail.com>		2021-02-16 22:15:33 -08:00
..
Properties	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
components	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
Program.cs	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
README.md	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
SecretStoreConfigurationProviderSample.csproj	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
Startup.cs	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
secrets.json	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00

README.md

Dapr secret store configuration provider in ASP.NET Core

Prerequisites

Overview

This document describes how to use the Dapr Secret Store Configuration Provider sample to load Secrets into ASP.NET Core Configuration.

To load secrets into configuration call the AddDaprSecretStore extension method with the name of the Secret Store and a list of secrets descriptors or related metadata.

Using the Dapr Secret Store Configuration Provider ASP.NET Core example

1. Use Dapr to run the application

Use Dapr to run the application:

dapr run --app-id SecretStoreConfigurationProviderSample --components-path ./components/ -- dotnet run

2. Test the application

Run the following command in other terminal:

curl http://localhost:5000/secret

The response should read: "This the way"