[FEATURE] Detect stale flags #400
Labels
enhancement
New feature or request
Needs Triage
This issue needs to be investigated by a maintainer
question
Further information is requested
Requirements
Background
Consider this conversation [1]. Flagd can operate with multiple sync providers. These sync providers push flag configurations which get stored in the internal in-memory
store
[2].There could be occasions where individual providers shutdown, and disconnect for various reasons. For example, for an HTTP flag source, the source can undergo maintenance causing downtime. When this happens, flags stored internally could go stale
Proposal
As highlighted by the conversation [1], it could be beneficial to mark stored flag configurations to be
stale
and set stateReason.STALE
for evaluations. This makes sure flag configurations served by flagd are consistent with their sources.Update
Given that we do not have a
stale
sate in existing evaluation reasons [3], a good alternative is to utilizeCACHED
state[1] - #297 (comment)
[2] - https://github.com/open-feature/flagd/tree/main/pkg/store
[3] - https://docs.openfeature.dev/docs/specification/types#resolution-details
The text was updated successfully, but these errors were encountered: