Hide the new virtual registry scopes behind a feature flag
What does this MR do and why?
Do not display the new scopes read_virtual_registry and write_virtual_registry while we're still working on it.
References
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
How to set up and validate locally
On the MR branch, the new scopes read_virtual_registry and write_virtual_registry should only be visible (see screenshot) if one or both of the feature flags virtual_registry_maven and dependency_proxy_read_write_scopes are enabled.
You can check for this in the UI by clicking the Add new token button in these places:
- User Settings -> Personal Access Tokens: http://gdk.test:3000/-/user_settings/personal_access_tokens
- Group page -> Settings -> Access Tokens: http://gdk.test:3000/groups/flightjs/-/settings/access_tokens
- Project page -> Settings -> Access Tokens: http://gdk.test:3000/flightjs/Flight/-/settings/access_tokens
- Admin -> Users -> (pick a user) -> Impersonation Tokens tab: http://gdk.test:3000/admin/users/reported_user_17/impersonation_tokens
Related to #336800 (closed)
Edited by Radamanthus Batnag