OpenFeature standard support

[MarcinGil]

OpenFeature (https://openfeature.dev/) strives to provide an independent standard for working with feature flags.

A standard access library is called a 'provider' in OpenFeature ecosystem. There are several providers for many vendors already provided there: https://openfeature.dev/ecosystem.

Having FeatureHub provider would greatly ease the integration.

Describe alternatives you've considered
Alternative solution to use directly FeatureHub's SDK is basically a vendor lock-in and my organization is more likely to adopt OpenFeature supported provider.

https://openfeature.dev/
https://openfeature.dev/ecosystem

[rvowles]

Hi Marcin - we are aware of it. Its certainly something we will need to implement in the near future.

[IrinaSouth]

We can add this to our roadmap. Community help on this would be much appreciated.

[MMartyn]

This seems promising in terms of not needing to maintain separate SDKs for OpenFeature, but instead expose a compatible API.

[MMartyn]

This seems promising in terms of not needing to maintain separate SDKs for OpenFeature, but instead expose a compatible API.

Actually, I played with this a little and I think we would lose the well designed fallback (cached local eval) and update mechanisms (SSE) if we used the ofrep. So IMO language specific wrappers of the FeatureHub SDKs for OpenFeature would be the path to go.

[aairey]

It is still possible to use SSE by having some API integration like Growthbook has recently done in their provider.

It would be really nice for us so that we can fully rely on the OpenFeature SDK in code.