Use "Environment spec" everywhere instead of "Environment scope"
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem
Today, there is a naming mismatch on the functionality for scoping environments.
- Clusters calls "Environment scope"
- Secret Variables calls "Environment scope"
- Feature Flag calls "Environment spec"
We should use the same terminology in order to avoid confusion.
NOTE: We use the word at the UI-level, not just Documentaion-level. So that we need to rename frontend components as well
Edited by 🤖 GitLab Bot 🤖