Support the configuration API for generic configuration providers
- Dominant language
- C#
- Stars
- 12k
- Forks
- 703
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 36
Description
### Feature request type
enhancement
### Is your feature request related to a problem? Please describe
Currently, when running the garnet server we must provider either command-line arguments or a `garnet.conf` JSON file.
By adopting the https://learn.microsoft.com/en-us/dotnet/core/extensions/configuration we will be able to use any configuration provider and require less manual work for maintaining the [Options](https://github.com/microsoft/garnet/blob/0f32b57e77f2abd19990b387747ece82474ed566/libs/host/Configuration/Options.cs) file
### Describe the solution you'd like
building on top of #579 we would call `builder.Configuration.AddEnvironmentVariables(prefix: "GARNET_")` (see https://learn.microsoft.com/en-us/dotnet/core/extensions/configuration-providers#prefixes)
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with libs/host/Configuration/Options.cs and the configuration changes from issue #579. Trace how the Garnet server currently reads command-line arguments and garnet.conf, then compare that flow with the .NET configuration API. Done means the server can use generic providers, including environment variables with the GARNET_ prefix, while preserving existing configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100