Operations and Kubernetes option should be omitted when repository or builds are disabled
requested to merge 47631-operations-kubernetes-option-is-always-visible-when-repository-or-builds-are-disabled into master
What does this MR do?
When repository
or builds
were disabled both Operations
and Kubernetes
option were shown in the sidebar, which would return in a 403/404 (depending on permissions) and the Kubernetes
page working as normal. These pages should be omitted when the scenario is verified.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Before
After
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Conform by the code review guidelines
-
Has been reviewed by a UX Designer -
Has been reviewed by a Frontend maintainer -
Has been reviewed by a Backend maintainer -
Has been reviewed by a Database specialist
-
-
Conform by the merge request performance guides -
Conform by the style guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them -
Internationalization required/considered -
End-to-end tests pass ( package-and-qa
manual pipeline job)
What are the relevant issue numbers?
Closes #47631 (closed)
Edited by Rémy Coutable