Group (Multi-Env) Flags
Group Flags (available in Multi-Environment projects) allow you to manage a single feature flag across multiple environments like Development, Staging, and Production from a single interface.
Creating a Group Flag
Section titled “Creating a Group Flag”- Enter a Multi-Environment Project.
- Click New Group Flag.
- Provide a Name and Description.
- Configure the default settings for each of your defined environments.
- Click Create.
Environment Isolation
Section titled “Environment Isolation”The core benefit of Group Flags is environment isolation. Each environment you’ve added to the flag can be managed independently.
Per-Environment Toggles
Section titled “Per-Environment Toggles”In the Group Flags table, you will see a toggle for each environment. Toggling “on” for dev will not affect the prod state.
Per-Environment Traffic
Section titled “Per-Environment Traffic”You can set different rollout percentages for different environments. For example:
dev: 100%staging: 50%prod: 0% (disabled)
Per-Environment Cohorts (Overrides)
Section titled “Per-Environment Cohorts (Overrides)”You can define specific cohorts for an environment.
- Override: If you set a cohort for the
devenvironment, the system will use that list and ignore the global flag-level cohorts for requests targetingdev. - Fallback: If an environment has no specific cohorts defined, it will fall back to using the global cohorts defined on the Group Flag.
- Configuration: These can be added or updated by clicking the Update icon for a specific environment in the Group Flags table.
Targeting Environments via API
Section titled “Targeting Environments via API”When querying a Group Flag, you must specify the environment using the env parameter:
GET https://api.rocketflag.app/v1/flags/{flag_id}?env=productionIf the env parameter is missing or does not match an environment defined for that flag, the API will return a 404 Not Found.