Geo Primary Verification API: GET api/v4/admin/data_management/:model/:id

Why are we doing this work

This work will be behind feature flag geo_primary_verification_view

We are building a view for customers to manage their instance's data and verify primary data integrity for Geo Improve primary verification experience (&16554)

important: This endpoint should be marked as experimental or beta until this work is complete to avoid issues with deprecations or removals as we explore what is needed.

note: The proposed endpoint may be changed based on decisions on the routing

What is needed in this change

This change is focused on creating an endpoint similar to Geo Primary Verification API: GET `api/v4/admin... (#537707 - closed), however, it will return a single record rather than a list based on the :id parameter.

Example response

important: This is very much a POC and could end up needing more/less than this response

{
  "id": "4",
  "modelClass": "Project",
  "createdAt": "2025-03-10T19:15:13Z",
  "file_size": "181",

  "checksumInformation": {
    "checksum": "1395a9bd59ff0e7d2207bd9cde6b67ee4a2f56fd",
    "lastChecksum": "2025-04-23T15:34:06Z",
    "checksumState": "FAILED",
    "checksumRetryCount": 3,
    "checksumRetryAt": "2025-04-23T15:38:06Z"
   "checksumFailure:" "Project cannot be checksummed because it does not exist"
  }
}

Relevant links

Implementation plan

This is an extension from #537707 (closed). A simple plan would be to:

  1. add a new :id route param to the existing DSL;
  2. find and return the corresponding model record.
Edited by 🤖 GitLab Bot 🤖