Geo: Create link between registry and model

What does this MR do and why?

Closes #577986 (closed)
Frontend for Geo Registry API: Add data-management-details-path (!221956 - merged)
Part of this change is behind a feature flag :geo_primary_verification_view

This change introduces the ability to link back from a Geo Registry => Data Model that it is replicating. This makes it a bit easier for support and customers to understand the linkage between the records across their Geo instances.

Additionally, even if the feature flag is disabled, we updated the UI text to better reflect the data model rather than simply provide a identifier with no context.

References

Screenshots or screen recordings

Demo

List View

Before After
List_Before List_After

Details View

Before After (w/ FF) After (w/o FF)
Details_Before Details_After Details_After__No_FF_

How to set up and validate locally

Setup Geo (optional)

Important: To properly test Geo you will need a separate GDK setup. Setup is straightforward but takes some time. Another option is to validate the code functionally and if needed schedule a call to sync and I can screen share my instance.

  1. Ensure no other GDKs are running. gdk stop/gdk kill
  2. Open an empty directory and install and run Geo with the one-line command found on the Easy installation instructions
  3. Access your primary and secondary Geo instances via 127.0.0.1:3000 and 127.0.0.1:3001.

Testing

  1. Enable the feature flag Feature.enable(:geo_primary_verification_view)
  2. Access your primary GDK Geo Page (127.0.0.1:3000/admin/geo)
  3. Scroll down to the secondary site
  4. Click a record link (ex. Project Repositories)
  5. Ensure list view has Model record with the model name (ex. Project/3)
  6. Click into a record
  7. Ensure there is now a link on the right side next to Model record
  8. Click the link
  9. Ensure it takes you to that model record in the Data management view

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #577986 (closed)

Edited by Zack Cuddy

Merge request reports

Loading