Environment
- dbdeployer version: 2.2.3
- Topology: galera --with-proxysql
Describe the bug
When deploying with --with-proxysql, dbdeployer deploys and starts the instances before checking whether proxysql is present, and then fails if it isn't.
Steps to reproduce
$ go run . deploy replication 13.0 --topology=galera --with-proxysql
# 13.0 => 13.0.0
Installing and starting node 1
.. sandbox server started
Installing and starting node 2
...... sandbox server started
Installing and starting node 3
..... sandbox server started
# Pre-exit cleanup.
#1 - Executing RmdirAll( /var/run/media/fred/DATA/DBDEPLOYER/sandboxes/galera_msb_13_0_0)
ProxySQL deployment failed: proxysql binary not found: proxysql binary not found in PATH: exec: "proxysql": executable file not found in $PATH
exit status 1
Expected behavior
Check that proxysql is present before deploying
Actual behavior
It checks AFTER
Environment
Describe the bug
When deploying with --with-proxysql, dbdeployer deploys and starts the instances before checking whether proxysql is present, and then fails if it isn't.
Steps to reproduce
Expected behavior
Check that proxysql is present before deploying
Actual behavior
It checks AFTER