Problem

Often feature flags are tied to pull requests, GitHub issues, or other internal documents

It would be nice if we had a way to record and track generic flag metadata per flag.

This lines up with the OpenFeature flag metadata type as well: https://openfeature.dev/specification/types/#flag-metadata

Ideal Solution

This is a large feature request as it will touch almost all of the code including:

• API GRPC + Rest
• UI
• Storage (Relational and Declarative)
• Import/Export
• Validation (flipt validate)
• SDKs (at least open feature)

I think it will however unlock potential future features

I've created a mockup of the UI:

The gist is:

• Support generic key/value pairs per flag
• Keys will be strings
• Values can be strings, bools or numbers
• Likely store these as JSON or individual rows in backing datastores (relational)
• Flag metadata should likely be returned on evaluation, per the OpenFeature spec (link above)

Again we need to break this down into smaller issues to track the various pieces above, but from an API perspective this could be either added as fields to the existing UpdateFlag request, where all of the metadata would need to be provided at once on update, or we could add new APIs like CreateFlagMetadata, UpdateFlagMetadata, DeleteFlagMetadata.

Wanted to open this up for discussion

Search

• I searched for other open and closed issues before opening this

Additional Context

No response

_{From SyncLinear.com | FLI-786}