Update conditions when the artifact registry menu is displayed
🌝 Context
As part of the Google Artifact Registry Integration for Contai... (&12365 - closed), in Adds menu entry for Google Artifact registry (!140086 - merged) a sub menu entry Google Artifact Registry
was added to the Deploy
menu.
As part of the verifications of Consolidate all google cloud support feature fl... (!145918 - merged), we noticed that this submenu would be displayed if:
- The saas only feature is enabled.
- If the feature flag is enabled. Changed in Consolidate all google cloud support feature fl... (!145918 - merged).
- If the user is
reporter+
. That was implemented in Introduce dedicated permission for Google Cloud... (!145264 - merged).
The problem is that the features behind this sub menu entry will require two project integrations:
If any one of them is missing or not enabled, screens of the Google Artifact Registry
sub menu will not work at all.
This MR will check for the two integrations as part of the conditions to display the sub menu entry.
⚙ What does this MR do and why?
- Updates when the
Google Artifact Registry
sub menu entry is displayed. When all these conditions are met:- the saas only feature is available.
- the feature flag is enabled.
- the user is reporter+.
- the artifact registry integration is operating.
- the IAM integration is operating.
- Update the related specs.
🏁 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
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
For a project without any integrations but with the feature flag enabled and a reporter+
user.
Before | After |
---|---|
⚗ How to set up and validate locally
Follow !145264 (merged)
Play with the integrations. For example, disable one of them and see how the submenu entry is not displayed.