Migrate environment header to vue
What does this MR do?
As part of the Pajamas migration, this #254258 (closed) is about using a vue modal for the stop button in the Environments detail page. Since the whole page was written in HAML, I decided to break it down and migrate the header part to vue.
This MR also removes a few QA tests as now we can write unit tests in the frontend to test the functionality.
Screenshots (strongly suggested)
Here's a screenshot that displays the two header bars. The one in red is HAML and the one in green is Vue. The buttons are slightly different but that should be because we now use our own component library directly instead of relying on css classes. This screenshot will include all functionalities, so if you test locally some of the buttons may be missing due to permissions.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #254258 (closed)