Block users without permission to add protected environments to feature flags
Release notes
Problem to solve
As a manager of production, I don't want developers to turn on/off feature flags in production. However, as a developer, I want to be able to turn on/off my feature during development (not on production)
Intended users
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Priyanka (Platform Engineer)
User experience goal
The user should be able to safeguard the feature flag enablement or disablement from specific high-risk environments such as production.
Proposal
This should be behind a feature flag until we implement #281832!
We will user users that are defined as "allowed to deploy" to protected environments as the permission model for feature flags strategies.
- Users that are allowed to deploy to protected environments can add protected environments to a feature flag strategy.
- Users that are not allowed to deploy to protected environments can not add protected environments to a feature flag strategy.
The BE should block users that do not have appropriate permissions to add/remove protected environments to a feature flag strategy.
They should also not be allowed to toggle a feature flag that includes a protected strategy. (Can this be included in the same iteration or should this be split into another issue?)