Geo: dynamic primary / secondary version lookups
The following discussion from !4353 (merged) should be addressed:
-
@nick.thomas commented on a discussion: (+3 comments) Since it would allow us to remove some keys from the initializer, I'll create a follow-up for it, but I don't consider it high-priority :)
Currently, the Geo nodes Vue component in https://gitlab.com/gitlab-org/gitlab-ee/blob/v10.5.8-ee/ee/app/assets/javascripts/geo_nodes/store/geo_nodes_store.js#L41 / takes a hard-coded primaryVersion
and primaryRevision
. These can only be filled in reliably from outside the component if the code is being used on the primary; however, it can be run on the secondaries as well.
These values are used to determine whether a secondary is running the same code version as the primary or not.
Since the vue component pulls the current version and revision from the primary in the same way it pulls them from the secondaries, we should be able to handle all this internally to the component, with no need to pass in the values manually.
I don't consider this high priority, so I'll just mark it as tech debt.