open-feature / open-feature/protocol
[Tracking] Implement OFREP Configuration Pattern Across SDK Clients
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 56
- Forks
- 7
- Avg merge
- 1h 54m
- Merged PRs (30d)
- 1
Description
Overview
This parent issue will track the implementation of the SDK configuration pattern—adopting environment variables as outlined in issue #53 across the various OFREP SDK client languages supported by the OpenFeature Protocol project.
Goal
Ensure that each OFREP SDK client allows users to configure via standardized environment variables (as defined by the ADR) to improve flexibility and consistency.
Scope
- Create or update SDK clients to support environment variable-based configuration per ADR recommendations.
- Document the supported variable names and their expected values/types across SDKs (e.g.,
OFREP_ENDPOINT,OFREP_HEADERS,OFREP_TIMEOUT_MS). - Track compatibility/migration concerns in each SDK.
References
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 issue #53 and the ADR it references to identify the required environment-variable pattern. Then inventory the supported OFREP SDK client languages and their configuration entry points. Done means each client supports the standardized variables and the supported names, values, types, and migration concerns are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100