Closes https://github.com/datagouv/data.gouv.fr/issues/1395 (partly). This ticket has been split into 5 PRs for easier reviewing:
1) Refactoring DB methods for new routes: PR #112 (MERGED)
2) Refactoring of old routes PR #117
3) This PR: Adding new route to gather informations from a resource in the catalog (ex : url, priority, etc.) PR #120
4) Adding new route to force a crawl PR #118
5) Adding resource statuses and a resource status route: PR #119
Details of this PR:
Create a new POST route /api/checks/ to force a new crawl on a specific resource_id or url. Note: no authentification in this PR yet, I think we should do it, but in another PR as this one is already big
Create a new related test tests/test_api.py::test_api_resource_created
Create a fixture for inserting a fake resource into DB
Needs to be reviewed AFTER PR #117.
Closes https://github.com/datagouv/data.gouv.fr/issues/1395 (partly). This ticket has been split into 5 PRs for easier reviewing: 1) Refactoring DB methods for new routes: PR #112 (MERGED) 2) Refactoring of old routes PR #117 3) This PR: Adding new route to gather informations from a resource in the catalog (ex : url, priority, etc.) PR #120 4) Adding new route to force a crawl PR #118 5) Adding resource statuses and a resource status route: PR #119
Details of this PR:
/api/checks/to force a new crawl on a specificresource_idorurl. Note: no authentification in this PR yet, I think we should do it, but in another PR as this one is already bigtests/test_api.py::test_api_resource_created