Skip to content

feature: add standard set of "ambient" props to context #851

Closed
@toddbaert

Description

We already need to add the flag_key to the context to improve our bucketing algorithm, see setFlagdProperties in the json_evalutor.

We should consider what other properties could be useful, and add them under some sort of namespace to the context. A list could include:

  • currentTimestamp
  • a variable indicating if this is an RPC implementation or an in-process implementation?

I kept thinking about things like version (the version of flagd) or connection_type (HTTP vs gRPC), but these would be unreliable and inconsistent between flagd RPC and in-process implementations. We should come up with a list that's relevant to all models, it think.

cc @craigpastro

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions