open-feature / open-feature/flagd
[DOCS] Establish provider configuration consistency guidelines and rules
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
Review the consistency of and enforce
- Strict requirements for env-vars and configuration options (the canonical set should be kept here, and updated if needed)
- Review existing implementations for inconsistency
Contributor guide
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
Start with the canonical provider configuration reference at flagd.dev/reference/specifications/providers/#configuration, then review the existing provider implementations for inconsistent environment variables and configuration options. Done means the canonical requirements are reviewed or updated and the existing implementations have been checked against them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100