Geo - Expose Replicable Names for each Geo Node Status Bar
Split off from #225529 (closed)
What/Why
The current process to adding a new data type to the Geo Node Status Bars is not scalable. More can be read about the extensive process here: #225529 (closed)
We need a way to create a generic and scalable way to add new data types to the Geo Node Status Bars via Geo Self Service.
This proposal exposes an issue of how the UI should best interpret what each replicable's label/name is in the UI.
Proposal
Proposal A: Blocked by #228700 (closed)
Add a user-friendly name to new RESTful endpoint (see above issue) for each data type in the response. This can be found as part of the replicator.rb
: https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/gitlab/geo/replicator.rb#L72
Ex:
{
// ...
lfs: {
name: 'LFS Objects', // <-- NEW KEY (self.replicable_name_plural)
enabled: true,
total: 5,
synced: 5,
failed: 0
},
// ...
}
Proposal B: Mentioned as part of @mkozono comments: #225529 (comment 377621471)
As part of geo/nodes/index.html.haml
also pass up a list of replicable names [lfs_objects, package_files, ...]
which would allow us to control the order shown in the UI. We would possibly need a way to also pass up the actual key they correspond to on the API response so that we could accurately match them up to what data set they represent.