-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: metadata conceptual doc #1550
Conversation
✅ Deploy Preview for polite-licorice-3db33c canceled.
|
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
1479d44
to
3fa75cd
Compare
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
## Metadata | ||
|
||
[Flag metadata](https://openfeature.dev/specification/types/#flag-metadata) comprises auxiliary data pertaining to feature flags; it's highly valuable in telemetry signals. | ||
Flag metadata might consist of attributes indicating the version of the flag, an identifier for the flag set, ownership information about the flag, or other documentary information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Q/SUGGESTION] just checked the flag-metadata OpenFeature link & wondering if we provide an example somewhere how this metadata could look like? otherwise we could add this here after this sentence in form of a short code snippet with example version of the flag, flag set id & ownership as said in text) - its a bit of a duplication but IMO easier to see when scrolling through the docs
Adds a bit of conceptual docs about metadata. We already have lots of detail on how to configure it, how it's merged in the
definitions
page, and how it's implemented in in-process providers.