From 6b8f3e968e42538d5e6334aae70acec3a98aaaed Mon Sep 17 00:00:00 2001 From: Anastas Stoyanovsky Date: Tue, 14 Jan 2025 13:31:06 -0500 Subject: [PATCH] Add link to RAG dev doc Signed-off-by: Anastas Stoyanovsky --- docs/adr-feature-gating.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/adr-feature-gating.md b/docs/adr-feature-gating.md index 64b8668..691792a 100644 --- a/docs/adr-feature-gating.md +++ b/docs/adr-feature-gating.md @@ -2,7 +2,7 @@ ## Context -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. +Motivated by the currently [in-progress RAG development](https://github.com/instructlab/dev-docs/pull/161) 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 individual experimental features. We do not need that level of fine-grained control at this time.