open-feature / open-feature/java-sdk-contrib
Add Provider Support for Cloud-based Parameter Stores (e.g., AWS SSM, GCP Parameter Manager, Azure App Config)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 81
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 6
Description
Description:
OpenFeature currently supports various providers for feature flag management. It would be valuable to extend this support by adding a provider (or a set of providers) for cloud-native parameter stores, which are commonly used in enterprise environments for storing configuration and secrets.
These parameter/configuration stores include:
- AWS Systems Manager Parameter Store
- Google Cloud Parameter/Secret Manager Manager
- Azure App Configuration / Key Vault
Adding support for these services would enable OpenFeature users to:
- Leverage existing cloud-native infrastructure
- Dynamically fetch feature flags or configuration values stored in these systems
- Improve consistency and reduce duplication across infrastructure and application layers
Proposed Solution:
Implement a separate providers per cloud that can:
- Connect securely to the respective parameter/config store
- Fetch values at runtime (optionally cache them)
- Map keys to OpenFeature flag format
- Handle authentication via cloud-native SDKs (IAM roles, service accounts, etc.)
Benefits:
- Seamless integration with existing cloud infrastructure
- Improved developer experience for cloud-first teams
- Encourages unified configuration management practices
Potential Challenges:
- Differences in data models and access patterns across cloud platforms
- Managing credentials securely across environments
- Standardizing behavior for flag evaluation
Related Links:
AWS Parameter Store
GCP Parameter Manager
Azure App Configuration
Notes:
If there's alignment with the OpenFeature roadmap, I’d be happy to collaborate on a proposal or contribute a reference implementation.
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
No files, tests, or entry points are named. Start by reviewing the linked AWS, GCP, and Azure documentation and checking the OpenFeature roadmap to define whether one provider or separate providers are in scope. Done should include an agreed scope for secure access, runtime fetching, key mapping, caching, and standardized flag evaluation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp, java
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100