Issue1267 queueName not working as expected because of upcoming feature

[petersilva]

There is a feature in the works (will not come with this version) to allow a single subscriber to use more than one queue, and more than broker to get messages from. This changes the semantics of the queueName and queueShare options in that they used to be global options that applied to all "subtopic" settings, but for multiple queues to work, they subtopic needs to apply to the queueName declared before it.

So some prep work was done for this feature... and it has the effect of implementing the change in how the options are interpreted before the actual benefit is there... the benefit will come in a future configuration. For now, people just have to change their configuration files to have the queue naming settings before the subtopic settings.

This set of patches:

• removes duplication (where the same topic would be added multiple times to subscriptions.)
• adds documentation about ordering to the options man page (subtopic vs. queueName and queueShare)
• adds logic to sr3 convert to move the queueName above the subtopic when converting.
• adds a warning message when a probably wrong configuration is encountered.

[github-actions[bot]]

Test Results

238 tests   236 ✅  1m 29s ⏱️   1 suites    1 💤   1 files      1 ❌

For more details on these failures, see this check.

Results for commit b10f0500.