Added option for backend to have a vhost override
Describe your changes Allows a backend to specify a different vhost to connect to than the one provided by the client. This allows easy migration of clients to new rabbitmq cluster with a different vhost.
Testing performed Run setup in production on live rabbitmq cluster with clients using default vhost '/' and redirecting them to other vhosts
Additional context Prob missing a few things, please let me know what improvements i can make
@adamncasey thanks for the review, VHOST remap does sound like a better solution, i take it when we get the open package from the client, we would then look up the mapping and update it?
Will have to wait a few weeks till i get some time to try that change