Register temporary files (like orthoready) for automatic removal
It's important to clean-up temporary files as soon as they are no longer required in order to avoid disk saturation.
Workarounds like #52 (closed) are possible, but at the cost of disabling the factorisation of some processing.
We could remove the oldest ortho-ready products, but without any guarantee they won't be useful later. This could be possible that with requests on wide time ranges, the number of products for a same S1 tile is superior to the arbitrary threshold used to clean-up old files.
The only solution that would scale is to change the way tasks dependency tree is built. It needs to encompass all S2 tiles (instead of a single one at the time). This could be done after #32 (Register image downloading as Dask tasks). This way, once each S2 images that depend on an ortho-ready S1 product have been produced, the temporary product could be safely removed.
Ideas:
- the requested products should be sorted by time stamp
- removal of temporary files could be a new task, automatically generated through graph analysis (non-requested products used as inputs)