Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-01-11 00:08:30 +01:00
Code Issues Projects Releases Wiki Activity

docs(sdks): gradual rollout: custom stickiness -> point to SDK table

Browse Source 
It appears that we've forgotten to update this bit of info regarding
the SDKs' compatibility. To avoid having the same data in multiple
places, let's instead point the user to the compat table.
This commit is contained in:
Thomas Heartman 2021-12-17 13:46:54 +01:00
parent 8a38b9e456
commit 291e8689fb
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/docs/user_guide/activation-strategies.md
View File

@ -47,11 +47,14 @@ This strategy has the following modelling name in the code:
- **flexibleRollout**
### Customize stickiness (beta) {#customize-stickiness-beta}
### Custom stickiness (beta) {#custom-stickiness}
By enabling the stickiness option on a custom context field you can use it together with the gradual rollout strategy. This will guarantee a consistent behavior for specific values of this context field. NB! this feature is currently only supported by the following SDKs:
:::note
This feature is currently in beta and is not yet supported by all our SDKs. Check out the [SDK compatibility table](../sdks/index.md#server-side-sdk-compatibility-table) to see what SDKs support it at the moment.
:::
By enabling the stickiness option on a custom context field you can use the custom context field to group users with the gradual rollout strategy. This will guarantee a consistent behavior for specific values of this context field.
- [unleash-client-node](https://github.com/Unleash/unleash-client-node) (from v3.6.0)
## IPs {#ips}