Best approach for using existing database for evaluation context?

[amweiss]

Rather than having every request to flipt have to include all possible data in the request context, I was considering how we could have it hooked into an existing user database and only require the unique id for lookup of additional data.

It seems like hooking into the server is not possible today, and it would have to be deeper into somewhere like

flipt/internal/server/evaluator.go

Line 189 in de4da94

v := r.Context[c.Property]

to make it have what is needed. So, my thought was building another service that wraps flipt that everything calls that only takes in the user id and then fetches whatever is needed for the other context items.

Am I missing anything? Server side it could be easier to pull in from other places in the context, but from client side I think we need to build something between the client and flipt.

[markphelps]

Rather than having every request to flipt have to include all possible data in the request context, I was considering how we could have it hooked into an existing user database and only require the unique id for lookup of additional data.

You are literally reading my mind. Can you send me an email to mark at flipt.io ? I would love to share this RFC I've been working on about this exact thing and get your feedback. I think it is currently from the perspective of Flipt also running the user to context database, but I love the idea of making it pluggable for an org to run its own.