Geo Node Status 2.0 - Vuex
What does this MR do?
Closes #287945 (closed)
Broken off from and set to power the UI here: !53090 (closed)
Works towards the Geo 2.0 Redesign: &4712 (closed)
This change is the Vuex Store to be used to power the new Geo UI. The main responsiblities of this store is to gather and merge the Node Details with its status. The other very powerful part of this store is the getters that are able to fetch the "replicables" in a generalized way as most of the data isn't constant.
Most of this logic is taken and refactored from these legacy files from the old UI (files set to be removed as part of: #287986 (closed)):
Legacy Store: https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/assets/javascripts/geo_nodes/store/geo_nodes_store.js
Legacy Service: https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/assets/javascripts/geo_nodes/service/geo_nodes_service.js
Legacy Event Hub: https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/assets/javascripts/geo_nodes/event_hub.js
How to fully test this change with the WIP UI
- Set up a Geo Primary/Secondary GDK
- Fetch the UI Branch: !53090 (closed)
- Activate the Feature Flag on your Primary GDK (
:geo_nodes_beta) - Navigate to
http://127.0.0.1:3000/admin/geo/nodes_beta - View UI
Screenshots (strongly suggested)
| /geo_nodes | /geo_nodes/status | Vuex State | |
|---|---|---|---|
| Screenshots |  |
 |
 |
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] 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 #287945 (closed)