The release includes stable versions the following features:
- the Evaluation API, providing application authors with consistent, vendor neutral, feature flag evaluation
- provider interfaces for flexible integration with a variety of feature flag systems
The specification documents associated with these features have been marked as
hardening, meaning breaking changes are no longer allowed and usage of these features are encouraged in production environments.
The release of these SDKs and the stabilization of the specification represent a culmination of efforts by a dedicated group of vendors, practitioners and subject matter experts.
Providers are already available for major vendors and popular community projects.
It's our hope that the efforts to stabilize the OpenFeature specification and SDKs will lead to more adoption of both OpenFeature and feature flagging in general, and promote a vibrant ecosystem around this increasingly important development pattern.
In addition to those mentioned above, experimental features available in the 1.0 SDKs include:
- hooks, for adding arbitrary behavior to feature flag evaluation, ideal for telemetry integration, validation, and logging
- the Evaluation Context interfaces, used as the basis for dynamic flag evaluation
Our goal in the upcoming months will be to harden our existing experimental features. Additionally, we'll work to develop and standardize new capabilities, including: client-side feature flagging, improved cloud native tooling, and implicit transaction-scoped data propagation of contextual attributes. Furthermore, we're working on SDKs for additional languages, including PHP, Python, and Ruby.
If you're interested in contributing or learning more about OpenFeature, please join our expanding and friendly community. Visit our GitHub, join the OpenFeature slack channel on the CNCF Slack instance, or hop into our bi-weekly community meeting.