About feature flags

Feature flags are the foundation of the CloudBees Feature Flags platform and can encompass many different types of logic and code.

Once a flag is created, you can easily enable and disable features in your application - giving you full control over how users are able to interact with your application.

Applications, Environments, and flags

Feature flags

There is an important relationship between Apps, Environments, and flags that allows for increased reusability and scalability.

Apps are the highest-level in our hierarchy, encompassing unique environments and flags underneath them. Apps should reflect the individual products and services your organization may have. It should not reflect one app in several states of servers.

Environments represent your deployment pipeline: production, staging, or testing. CloudBees Feature Flags supports working with multiple Environments. You can create an unlimited number of Environments and add Flags, Configs, and Experiments to each Environment.

Flags are shared between Environments.

Default values of flags

A flag default value is the value of the flag that is created when defining flags in the code. Default values are mandatory and flags cannot be created without them. They will be served when there is no configuration available (for any reason) or no other value overrides it.

A boolean flag is false by default. To override the value, pass the desired value to the flag.

A string flag (multivariate) has an explicit configuration for its default value.  In most languages, the first value would be the default value followed by an array of potential values.

Impact on the existing feature flags after deleting a user from the team

There is no impact on the existing feature flags after a user is deleted from the team. You can still use the feature flags that the deleted user created. The default feature flag values can be used.