Geo Primary Verification API: POST api/v4/admin/data_management/:model/:id/checksum
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 functionality will only be available if checksumming is enabled for the model.
This change is focused on creating an endpoint similar to Geo Primary Verification API: POST `api/v4/admi... (#537709 - closed), however, it will execute the action only on a single record based on the :id
Relevant links
- Routing discussion: Geo Primary Verification: Routing (#537677 - closed)
- Bulk Actions API Endpoint: Geo Primary Verification API: POST `api/v4/admi... (#537709 - closed)
Implementation plan
This follows from #537708 (closed). From the new :id route param, add a new checksum endpoint which:
- Finds the Replicator class associated with the Model passed;
- Check verification is enabled on this Replicable;
- If not, returns an error
- If yes, instantiates a Replicator object with the model record associated with the ID
- Runs
.verifyon the Replicator instance.