dotnet-sdk/examples/AspNetCore/SecretStoreConfigurationPro...
Yash Nisar 17f849b175
Remove .NET Core 3.1 support and standardize on .NET 6 (#1045)
* Remove .NET Core 3.1 support and standardize on .NET 6

Signed-off-by: Yash Nisar <yashnisar@microsoft.com>

* Remove support for .NET 5 as well

Signed-off-by: Yash Nisar <yashnisar@microsoft.com>

---------

Signed-off-by: Yash Nisar <yashnisar@microsoft.com>
2023-08-24 11:04:02 -07: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 Wait for sidecar in DaprSecretStoreConfiguration (#838) 2022-02-17 16:39:33 -08:00
README.md Remove .NET Core 3.1 support and standardize on .NET 6 (#1045) 2023-08-24 11:04:02 -07:00
SecretStoreConfigurationProviderSample.csproj Remove .NET Core 3.1 support and standardize on .NET 6 (#1045) 2023-08-24 11:04:02 -07:00
Startup.cs replaced license headers (#802) 2021-12-10 13:39:06 -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"