Hello Aaron, even later on my side! I´ve just been able to come back to this subject today and I´ve seen your last message (for some reason I didn´t see it before). I´ve done a simple test on my side, and, as you said it works as expected. Persistency shouldn´t be an issue for us as we can recover messages differently.
However, while, testing it, i´ve tried to create a queue or a topic endpoint on the “distant” VPN in order to take advantage of non-exclusive setup and have also within the VPN round robin messages to final clients but without success. I am new to solace and it´s advanced configuration so I must have misunderstood something. The idea was to create a queue, subscribe to > for example and then have the clients consume from the queue.
VPN 1 ---- Bridge with #share topic —> VPN 2 —> Queue ----> Client 1/Client2
Is this possible? I´m testing it fully from the UI with the samble kubernetes deployment.
Thanks so much for all your feedback.