Service stop order

Is it possible to control the stop order of the services? We start/stop a lot of environments as part of our CI and regression processes. When environments are stopped, they generate a lot of logging noise in our DataDog account. For example, if the postgres service stops prior to the app, the app generates many erroneous connection errors.

Ideally, Qovery would know that we click “stop” to stop services in reverse order of our pipeline. For example, first the application services and workers would be stopped, followed by any dependencies.

Is this doable today?