You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes you need to deal with the RabbitMQ connection string for other reasons. Therefor you've to parse the connection string and handle the different schemas (amqp or sql-style).
You already have a perfect implementation, the NServiceBus.Transport.RabbitMQ.ConnectionConfiguration.Create method. Unfortunately it cannot be used because the ConnectionConfiguration class is private.
Please make this class public so it can be re-used.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
@twenzel thanks for raising this and the corresponding PR, to better evaluate the proposal can you share some details on the use case that requires the connection string to be parsed? This functionality would likely sit better in the RabbitMQ client, have you checked if something similar is available in the RabbitMQ client library?
Unfortunately,I didn't found anything in the RabbitMQ client library.
Use case: I've an connection string (might be amqp or NServiceBus) and want to fill the ConnectionProperties of the RabbitMQ.Client.ConnectionFactory.
This whole story is done to because we want to have 2 different ConnectionStrings. One with administrative permissions and one regular permissions. The "Admin-ConnectionString" is used to create the infrastructure (Exchanges and Queues).
Describe the suggested improvement
Sometimes you need to deal with the RabbitMQ connection string for other reasons. Therefor you've to parse the connection string and handle the different schemas (amqp or sql-style).
You already have a perfect implementation, the
NServiceBus.Transport.RabbitMQ.ConnectionConfiguration.Create
method. Unfortunately it cannot be used because theConnectionConfiguration
class is private.Please make this class public so it can be re-used.
Additional Context
No response
The text was updated successfully, but these errors were encountered: