feat: Add Flipt provider

[atmask]

Overview

This PR implements the Flipt provider by wrapping around the OFREP Provider and leveraging Flipt's OFREP api

Discussion Points:

• Should we support passing the namespace in the constructor this way or just leave it up to users to do it themselves via the generic headers_factory (like they would need to for authentication)

Related Issues

Fixes #89

How to test

Unit Tests: From the base of the package run hatch test

Local Usage: Go to the base of the new packager (i.e. provider/openfeature-provider-flipt), run pip install -e ., and then open a python repl with python3:

from openfeature import api
from openfeature.contrib.provider.flipt import FliptProvider
api.set_provider(FliptProvider(base_url="<flipt instance>", namespace="<your namespace>"))
client = api.get_client()
client.get_boolean_value("<your feature flag key>", True)

[markphelps]

lgtm! just curious if this gives end users much over the generic Python OFREP impl? Is the end goal of OFREP to make it easier to implement provider specific sdks or to be 'the' SDK for all providers that support it?

cc @beeme1mr

[beeme1mr]

I'm fine with the OFREP provider being extended to make it work more seamlessly. It's really up to you and Mark. I believe Flipt also has an SDK that supports in-process evaluation. That would likely be a more performant option.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.65%. Comparing base (d3e3b94) to head (1bc44e2).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #143      +/-   ##
==========================================
+ Coverage   94.39%   94.65%   +0.26%     
==========================================
  Files          14       14              
  Lines         749      749              
==========================================
+ Hits          707      709       +2     
+ Misses         42       40       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[atmask]

@beeme1mr kk, sounds good. I'll leave that ask up to @markphelps to give direction on. I had thought of wrapping around the existing Python SDK for Flipt but OFREP seemed quicker and easier option to get support out (I'd like to be able to consume this api). I can re-work it but it'll just take some more time to re-write the implementation

[markphelps]

@atmask lgtm! thank you!! we do have an inprocess evaluator like @beeme1mr mentioned, although I think it would be classified as a client provider in the OF world. the only thing to note is that Flipt added OFREP support in Flipt v1.47.0, so these endpoints wont exist in any versions of Flipt before this

[beeme1mr]

Could you please registry this provider in the release please manifest and config? Once that's in place, we should be good to release. Thanks!

• https://github.com/open-feature/python-sdk-contrib/blob/main/.release-please-manifest.json
• https://github.com/open-feature/python-sdk-contrib/blob/main/release-please-config.json

[atmask]

@beeme1mr Yes! Just pushed the manifest & config updates

[atmask]

@beeme1mr What blockers remain for getting this merged and releasing? Is release to pypi automated atm?

[beeme1mr]

What blockers remain for getting this merged and releasing? Is release to pypi automated atm?

Sorry, the blocker is me. I'll take care of this ASAP.