You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this schema change, flag metadata can now be stored in flag configuration files. Specifically, these can contain things like version and flag set id information so that consumers can use this data in flag evaluations, caching, telemetry etc.
We need to add this metadata into flags which are evaluated in RPC mode as well as in OFREP. That means modifications to the handlers here and here, respectively. Essentially, we need to take the properties from the flag definition and include them in the response in the flag metadata field.
@aepfli@toddbaert@beeme1mr Could you please take a look and let me know if I'm on the right track, or if I'm off course? I'll continue refining the PR in subsequent iterations.
With this schema change, flag metadata can now be stored in flag configuration files. Specifically, these can contain things like
version
and flag setid
information so that consumers can use this data in flag evaluations, caching, telemetry etc.We need to add this metadata into flags which are evaluated in RPC mode as well as in OFREP. That means modifications to the handlers here and here, respectively. Essentially, we need to take the properties from the flag definition and include them in the response in the flag metadata field.
Acceptance criteria:
id
andversion
metadata (https://github.com/open-feature/flagd/blob/main/flagd/pkg/service/flag-evaluation/ofrep/handler.go)id
andversion
metadata (https://github.com/open-feature/flagd/blob/main/flagd/pkg/service/flag-evaluation/flag_evaluator_v2.go)The text was updated successfully, but these errors were encountered: