Skip to content

Commit

Permalink
Fix grammar
Browse files Browse the repository at this point in the history
Signed-off-by: Anastas Stoyanovsky <[email protected]>
  • Loading branch information
anastasds authored Jan 14, 2025
1 parent 7fb0508 commit 7ae9487
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/adr-feature-gating.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

Motivated by the currently in-progress RAG development in [dev preview scope](https://access.redhat.com/support/offerings/devpreview), there is a use case for introducing feature gating (sometimes equivalently called "feature flags"). The specific use case desired is to have default settings for feature gating in the product that can be overridden using environment variables.

One common pattern is per-feature gating, i.e., configuration per-feature. This fine-grained control might be desirable in the future, especially to enable user segmentation for enable experimental features. We do not need that level of fine-grained control at this time.
One common pattern is per-feature gating, i.e., configuration per-feature. This fine-grained control might be desirable in the future, especially to enable user segmentation for individual experimental features. We do not need that level of fine-grained control at this time.

There is precedent [in OpenShift](https://docs.openshift.com/container-platform/4.17/nodes/clusters/nodes-cluster-enabling-features.html) for enabling sets of features based on support scope. Following this pattern would be consistent with OpenShift terminology and meets our needs at this time.

Expand Down

0 comments on commit 7ae9487

Please sign in to comment.