Geo primary verification: Add a GET record query to data_management API
What does this MR do and why?
This adds a single record query to data_management API, in order to allow users and the future front-end to query data about a specific record of a specific model, based on its primary ID value.
References
Geo Primary Verification API: GET `api/v4/admin... (#537708 - closed)
How to set up and validate locally
- Enable the feature flag in Rails console
Feature.enable(:geo_primary_verification_view); - Test the new API endpoint as an admin user:
# Replace YOUR_ADMIN_TOKEN with an actual admin personal access token
curl -H "Authorization: Bearer YOUR_ADMIN_TOKEN" \
"http://localhost:3000/api/v4/admin/data_management/lfs_object/1"
- Verify the response contains the expected fields:
-
id,model_class,created_at - Geo verification fields:
checksum,checksum_state,checksum_retry_count, etc. -
addl_infowith additional model attributes
- Test with different model names:
curl -H "Authorization: Bearer YOUR_ADMIN_TOKEN" \
"http://localhost:3000/api/v4/admin/data_management/snippet_repository/1"
- Test with different model IDs:
curl -H "Authorization: Bearer YOUR_ADMIN_TOKEN" \
"http://localhost:3000/api/v4/admin/data_management/snippet_repository/20"
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 #537708 (closed)