Problem Statement
Currently the .NET SDK requires calling ReplaneClient.Get() directly.
For ASP.NET Core applications, it would be better to provide an IConfiguration provider:
builder.Configuration.AddReplane(...)
Benefits:
- Works with IOptions
- Works with IOptionsMonitor
- No business code changes
- Compatible with existing ASP.NET Core configuration ecosystem
- Supports runtime configuration reload
Example:
builder.Configuration
.AddReplane(options =>
{
options.ApiKey = "...";
});
Proposed Solution
I would like to see native support for Microsoft.Extensions.Configuration.
The SDK currently requires calling Replane APIs directly, but ASP.NET Core applications usually consume configuration through IConfiguration.
A Replane IConfigurationProvider implementation would allow developers to use Replane with:
- IConfiguration
- IOptions
- IOptionsMonitor
- Configuration binding
- Dynamic configuration reload
This would provide a more idiomatic ASP.NET Core experience.
Alternatives Considered
No response
Feature Area
Client API
Additional Context
No response
Problem Statement
Currently the .NET SDK requires calling ReplaneClient.Get() directly.
For ASP.NET Core applications, it would be better to provide an IConfiguration provider:
builder.Configuration.AddReplane(...)
Benefits:
Example:
builder.Configuration
.AddReplane(options =>
{
options.ApiKey = "...";
});
Proposed Solution
I would like to see native support for Microsoft.Extensions.Configuration.
The SDK currently requires calling Replane APIs directly, but ASP.NET Core applications usually consume configuration through IConfiguration.
A Replane IConfigurationProvider implementation would allow developers to use Replane with:
This would provide a more idiomatic ASP.NET Core experience.
Alternatives Considered
No response
Feature Area
Client API
Additional Context
No response