leancodepl / leancodepl/corelibrary
Configuration validation
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 30
- Forks
- 4
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 3
Description
We don't have any means to validate system-provided (e.g. env variables, KeyVault) configuration. Having such mechanisms would be beneficial, esp. for first time prod deployments (or when the config changes).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by locating how system-provided configuration from environment variables and KeyVault enters the backend services, then define validation scope and completion criteria for first-time production deployments and configuration changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100