dapr / dapr/dotnet-sdk

secrets configuration provider - reload

Open
#1,030 1 comment 1 reaction 0 assignees View on GitHub
area/aspnetcore area/client/secrets kind/enhancement size/S
Dominant language
C#
Stars
1.2k
Forks
378
Avg merge
2d 1h
Merged PRs (30d)
6

Description

## Ask your question here
Hi All,

i'm using the secrets configuration provider like

```
var builder = WebApplication.CreateBuilder(args);
builder.WebHost.ConfigureAppConfiguration(config =>
{
var daprClient = new DaprClientBuilder().Build();
var secretDescriptors = new List
{
new DaprSecretDescriptor("eshopsecrets")
};
config.AddDaprSecretStore("secret-store", secretDescriptors, daprClient);
});
```

is there a way or best practice to reload in case of secrets change? for now i see it's only on app startup.
the azure keyvault configuration provider there is a reloadinterval. is something similar maybe?
https://learn.microsoft.com/en-us/aspnet/core/security/key-vault-configuration?view=aspnetcore-7.0

thanks!
Levente Pop

Contributor guide

Open the contributing guide

Research direction

Start with the ConfigureAppConfiguration and AddDaprSecretStore calls shown in the issue, then inspect the secrets configuration provider entry point and its existing tests. Compare the current startup-only behavior with the Azure Key Vault reload interval referenced in the issue. Done means the provider has a documented, tested way to observe secret changes and refresh configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.