Describe the bug
As of today when launching a dump creation process using the following route POST /dumps/ MeiliSearch returns a dumps_uid. This uid helps the user track the dump creation process using the dump status route GET /dumps/:dumps_uid/status.
If the user did not save the dumps_uid he will not be able to recover it as there is no GET /dumps/ route which could inform about the previous dumps creation.
The only solution is to go directly into the dump folder and look at the dump name. But this only works when the process succeeded.
To Reproduce
Steps to reproduce the behavior:
POST /dumps without saving the dumps_uiddumps_uidExpected behavior
There should be a GET /dumps/ route that gives you the history of dump creation and helps you recover any dump_uid.
Not for now, I think this route is relevant if you have a full http interface with upload, download... Which is not the case. Today's backup needs to have access to the file system to use them so the only way to have the backup list is to check the directory where backups are.
Most helpful comment
Not for now, I think this route is relevant if you have a full http interface with upload, download... Which is not the case. Today's backup needs to have access to the file system to use them so the only way to have the backup list is to check the directory where backups are.