1d9065aff1
Co-authored-by: Christopher Kolstad <chriswk@fastmail.com> Co-authored-by: Fredrik Strand Oseberg <fredrik.no@gmail.com> Co-authored-by: Ivar Conradi Østhus <ivarconr@gmail.com> Co-authored-by: Eco C <egilconr@gmail.com>
2.6 KiB
| id | title |
|---|---|
| control_rollout | Control rollout |
It is powerful to be able to turn a feature on and off instantaneously, without redeploying the application. The next level of control comes when you are able to enable a feature for specific users or enable it for a small subset of users.
In this guide you will learn how to control the roll-out (expose it to real users) of a new feature with the help of activation strategies.
Built in activation strategies
Unleash comes with a few common activation strategies. Some of them require the client to provide the unleash-context, which gives the necessary context for Unleash.
The built in activation strategies:
- default
- userWithId
- flexibleRollout
- remoteAddress
- applicationHostname
The default activation strategy
When you create a new feature toggle you will get the default activation strategy, if you don’t configure any specific strategies. The default activation strategy will always evaluate to true, given that the feature toggle is enabled.
The userWithId strategy
When we have deployed some new code to production it would be nice to enable the new feature for ourselves before we enable it to everyone else. To achieve this in Unleash you can use the userWithId activation strategy. This strategy allows you to specify a list of user IDs that you want to expose the new feature for.
A userId is how you identify users in your system (email, UUID, etc) and is provided as part of the Unleash Context to the client SDK.
Multiple activation strategies
In order to increase the exposure of the feature which is protected with the feature toggle you can configure multiple activation strategies on the same feature toggle.
In the example above we have configure two activation strategies, userWithId and flexibleRollout. If one of them evaluates to true the feature toggle is considered enabled. In the example we have enabled the feature toggle for usersWithId (me@mail.com and another@mail.com) in addition to 10% of the traffic.
Summary
You use activation strategies to control who the feature toggle will be enabled for. You can configure multiple strategies for a feature toggle, and they are considered in an OR fashion, meaning if one of them evaluates to true the toggle will be enabled.
If you need to limit the exposure (AND) you should look in to strategy constraints, which is the building block for that.