search

open-feature / ofep

A focal point for OpenFeature research, proposals and requests for comments
https://openfeature.dev
21 stars 15 forks source link

Transaction Context Propagation Proposal #32

Closed beeme1mr closed 1 year ago

beeme1mr commented 2 years ago

Relates to https://github.com/open-feature/spec/issues/81

morigs commented 1 year ago

Is distributed context propagation out of context? As a developer, how can I extract the current context in order to send it further (for instance, using OTel Baggage)? Perhaps this matter should be mentioned even if it's out of scope

beeme1mr commented 1 year ago

Hi @morigs, that's a good point. I'll explicitly state that distributed context propagation is out of scope of this OFEP. However, this OFEP is likely a prereq for distributed context propagation using OTel.

By the way, the demo environment includes a proof of concept for distributed context propagation. You can see it here.

moredip commented 1 year ago

I think this would be really beneficial for some runtimes (i.e. node), and is a really representative example of how the OpenFeature SDK could provide a very useful but fiddly-to-implement capability so that all the various providers don't have to figure it out themselves.

I would like to see if we could make the API as ergonomic as adding an attribute to an otel span - I think that's a close analog. Likewise it would be great it we could draw inspiration from how otel make the propagator registration as simple as possible for the simple case - maybe you've already done that.

moredip commented 1 year ago

@beeme1mr do you think you've gotten enough feedback on this that we could consider it accepted, and move on to speccing it out?