Dependencies
Model relationships between flags so Vexil can warn you before you accidentally break dependent features.
What is a dependency?
A dependency edge means "Flag B requires Flag A to be enabled." If you disable Flag A, Flag B becomes effectively inactive even if its own toggle is still on. Without this relationship modelled, it's easy to forget which flags rely on each other.
Adding a dependency
- 1Open the flag detail pageClick on any flag in the list.
- 2Go to the Dependencies tabYou'll see two sections: "Depends on" and "Required by".
- 3Click "Add dependency"Search for the parent flag by key name.
- 4Select and saveVexil checks for circular dependencies automatically and rejects anything that would create a cycle.
Cascade disable
When you try to disable a flag that other flags depend on, Vexil shows a warning modal listing all the flags that would be affected. You can:
- Cancel — leave everything as-is.
- Disable all — atomically disable the parent flag and every enabled flag that depends on it.
Cascade disable only affects flags in the current environment. Flags in other environments are not touched.
Dependency graph
The Graph page in the sidebar shows all flag dependencies across your organization as an interactive diagram. Nodes are colour-coded: green for enabled in production, muted for disabled, red for archived. Click any node to jump to that flag's detail page.