In what area(s)?
/area runtime
Describe the feature
Allow applications to get all secrets they've got access to from the secrets API, for example:
GET http://localhost:<daprPort>/v1.0/secrets/<secret-store-name>
[
{
"name": "secret1",
"keys": {
"key1": "value1",
"key2": "value2"
}
},
{
"name": "secret2",
"keys": {
"key1": "value1",
"key2": "value2"
}
}
]
This would make it significantly easier to create a .NET Configuration Provider that doesn't require the developer to pass the secret names directly in code when registering the provider (.NET Configuration Providers cannot lazily load configuration. They need to get all configuration from the underlying store at startup time). This behavior would be similar to the implementation of the .NET Configuration Provider for Azure KeyVault.
In what area(s)?
/area runtime
Describe the feature
Allow applications to get all secrets they've got access to from the secrets API, for example:
This would make it significantly easier to create a .NET Configuration Provider that doesn't require the developer to pass the secret names directly in code when registering the provider (.NET Configuration Providers cannot lazily load configuration. They need to get all configuration from the underlying store at startup time). This behavior would be similar to the implementation of the .NET Configuration Provider for Azure KeyVault.