fix(engine): update logical dump flow to start existing dump container (#383)
Description
Updated logic for logicalDump job to check if dump container is already present start it
Related issue
Examples
- start dblab server with logicalDump configuration and running
dblab_ld_xxx
container: - stopped
dblab_server
anddblab_ld_xxx
container - started
dblab_server
- logs from
dblab_server
,dblab_ld
container was identified and started:
Checklist
-
MR description has been reviewed -
MR changes are functionally tested -
MR does NOT have text changes OR there are text changes and they have been reviewed -
MR does NOT have API/CLI changes OR there are API/CLI changes and they have been reviewed -
MR does NOT have UI changes OR there are UI changes and they have been reviewed
Closes #383 (closed)
Edited by Artyom Kartasov