From 72e1bd7e2c1ea98964bd65b57b535f40fcb446be Mon Sep 17 00:00:00 2001 From: Nick Herro Date: Fri, 24 Jan 2020 00:02:22 -0500 Subject: [PATCH] chore: Update activation-strategies.md (#554) Fixes bold **SESSIONID** --- docs/activation-strategies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/activation-strategies.md b/docs/activation-strategies.md index 25a88d6512..2167b90646 100644 --- a/docs/activation-strategies.md +++ b/docs/activation-strategies.md @@ -30,7 +30,7 @@ A flexible rollout strategy which combines all gradual rollout strategies in to - **stickiness** is used to define how we guarantee consistency for gradual rollout. The same userId and the same rollout percentage should give predictable results. Configuration that should be supported: - **DEFAULT** - Unleash chooses the first value present on the context in defined order userId, sessionId, random. - **USERID** - guaranteed to be sticky on userId. If userId not present the behaviour would be false - - **SESSIONID - **guaranteed to be sticky on sessionId. If sessionId not present the behaviour would be false. + - **SESSIONID** - guaranteed to be sticky on sessionId. If sessionId not present the behaviour would be false. - **RANDOM** - no stickiness guaranteed. For every isEnabled call it will yield a random true/false based on the selected rollout percentage. - **groupId** is used to ensure that different toggles will **hash differently** for the same user. The groupId defaults to _feature toggle name_, but is overridable by the user to _correlate rollout_ of multiple feature toggles. - **rollout** The percentage (0-100) you want to enable the feature toggle for.