this playbook is meant to be run as a job only one time and not included in a ccm release
The idea behind the migration playbook is to transfer the latest state prior to CCM release of switching aqua from using a standalone db to a patroni instance.
The operational plan would be prior to running a CCM release, disable sync for aqua and run this job to get the latest state in patroni.
Updates:
Added a new playbook:
The idea behind the migration playbook is to transfer the latest state prior to CCM release of switching aqua from using a standalone db to a patroni instance.
The operational plan would be prior to running a CCM release, disable sync for aqua and run this job to get the latest state in patroni.