mirror of
https://github.com/Unleash/unleash.git
synced 2024-12-22 19:07:54 +01:00
40 lines
3.5 KiB
Plaintext
40 lines
3.5 KiB
Plaintext
---
|
|
title: Feature Flags
|
|
---
|
|
|
|
Feature flags are the central concept that we built Unleash around. In Unleash, feature flags are organized within [projects](../reference/projects.md). Feature flags can have different [activation strategies](../reference/activation-strategies.md) for each of their project's [environments](../reference/environments.md), and can also be given [variants](../reference/feature-toggle-variants.md) to facilitate A/B testing.
|
|
|
|
## Configuration options
|
|
|
|
Each feature flag has the following configuration options
|
|
|
|
| Option | Required? | Default value | Description |
|
|
| --- | --- | --- | --- |
|
|
| name | Yes | N/A | The feature flag's name. Must be URL-friendly according to [section 2.3 of RFC 3986](https://www.rfc-editor.org/rfc/rfc3986#section-2.3) and must be unique within your Unleash instance. Must be between 1 and 100 characters long, inclusive. |
|
|
| feature flag type | Yes | Release | The [feature flag's type](../reference/feature-toggle-types.md). |
|
|
| project | Yes | The [default project](../reference/projects.md). When created from a project page in the admin UI, that project will be the default value instead. | The [project](../reference/projects.md) that should contain the feature flag. |
|
|
| description | No | N/A | A description of the feature flag's purpose. |
|
|
| enable impression data | Yes | No | Whether to enable [impression data](../reference/impression-data.md) for this flag or not. |
|
|
|
|
## Environments
|
|
|
|
You probably won't want to use the same configuration to enable a flag in development as you do in production. That's why feature flags have different activation strategy configurations for each environment.
|
|
|
|
You can enable and disable a flag independently in each of the [project's environments](../reference/projects.md). When you disable a flag in an environment, it will always evaluate to false in that environment. When you enable a flag in an environment, the flag will evaluate to true or false depending on its activation strategies.
|
|
|
|
Refer to the [documentation on environments](../reference/environments.md) for more details on how environments work.
|
|
|
|
## Activation strategies
|
|
|
|
To enable a feature in an environment, you must assign it at least one activation strategy. A feature flag's activation strategies determine whether the flag gets enabled for a particular [Unleash context](../reference/unleash-context.md) (typically a user). When using multiple strategies in a single environment, only a single strategy needs to evaluate to true for the flag to get enabled for a user. Whenever Unleash evaluates a flag, it will evaluate strategies in the current environment until one of them resolves to true. If no strategies resolve to true, then the flag's value is false.
|
|
|
|
Refer to the [activation strategies documentation](../reference/activation-strategies.md) for a detailed description of all the built-in strategies.
|
|
|
|
## Variants
|
|
|
|
[Variants](../reference/feature-toggle-variants.md) adds another dimension of flexibility to feature flags. Each feature flag can be assigned any number of variants which will then get distributed amongst your users based on your choice of [context field](../reference/unleash-context.md#structure). You can find out more about variants in the [variants docs](../reference/feature-toggle-variants.md).
|
|
|
|
### Creating flags with payloads
|
|
|
|
While variants are most often used for A/B testing and the like, you can also use variants to assign a constant payload to a flag. If you give a flag only a single variant and that variant has a payload, then all users variants will receive that payload.
|