open-feature / open-feature/java-sdk-contrib
[OFREP] Implement support for OFREP Server SDK configuration using environment variables
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 81
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 6
Description
Overview
Implement support for OFREP SDK configuration using environment variables in the SDK.
Goal
Enable users of the OFREP to configure the client using standardized environment variables, improving flexibility and consistency across OpenFeature Protocol implementations.
Scope
Environment Variables to Support
The following environment variables should be implemented:
OFREP_ENDPOINT- The OFREP server endpoint (e.g.,http://localhost:2321)OFREP_HEADERS- Custom headers in comma-separated format (e.g.,"Authentication=Bearer 123,Content-Type=json")OFREP_TIMEOUT_MS- Request timeout in milliseconds (e.g.,5000)
Implementation Tasks
- Add support for reading
OFREP_ENDPOINTenvironment variable - Add support for reading
OFREP_HEADERSenvironment variable with proper parsing - Add support for reading
OFREP_TIMEOUT_MSenvironment variable - Ensure programmatic configuration takes precedence over environment variables
- Add validation and error handling for invalid environment variable values
- Update SDK documentation with environment variable usage examples
- Add tests for environment variable configuration
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 by locating the OFREP SDK configuration entry point and its existing programmatic configuration, then inspect how requests and timeout settings are represented. Implement handling for OFREP_ENDPOINT, OFREP_HEADERS, and OFREP_TIMEOUT_MS with programmatic values taking precedence, and add validation, tests, and documentation examples as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100