Trigger CSDS ingress on demand.
Changed onRuns all enabled CSDS ingress processors synchronously using the same retrieval and apply flow as the scheduled CSDS job. Processing continues if an individual processor fails, but the request returns an error after all processors have been attempted. If all failures are invalid record data returned by CSDS (including missing fields, invalid IDs and malformed dates), the response is 502 Bad Gateway. Unexpected AppReg failures, including a mixture of upstream validation and internal failures, result in 500 Internal Server Error. Successful processors' changes are not rolled back when another processor fails. The endpoint does not update the scheduled-run execution log and therefore does not suppress a subsequent scheduled run. Only callers with the admin role can trigger the operation.
Request
- Base URL/ (relative, and the document was published on a file host, not at the API’s origin)
- URL/admin/csds/trigger
- Authnone declared
Response
All enabled CSDS ingress processors completed successfully.
Changes
- info
added the non-success response with the status
- info
- info
endpoint added
- info