The issue:
--------------
If you are not adding, but simply renaming a channel in cr.yml, the slave configuration for the old channel name stays in place and one more configuration is created. It looks a bit confusing because only one configuration is described in cr.yml

How to reproduce:
--------------------------
I have this in my cr.yml

And this is the configuration in the DB:

If I update the cr.yml and change the channel name

I have the updated info in the replication_asynchronous_connection_failover table:

But I still have the old slave configuration:

It's not a big problem in itself, but maybe confusing, since only one configuration is described in cr.yml and only one configuration supports connection failover in this case

Possible solution:
------------------
The following command will clean up the configuration for the specified channel: