-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple hosts
to Bunny
#294
Comments
@bradrobertson why not add |
Do you mean something like |
@bradrobertson I'd just pass both to Bunny and let it do what's right. Hutch's job is to provide an opinionated set of conventions and a CLI daemon, not reinvent Bunny's features. |
Ya I understand what you're saying, but from what I can tell, Hutch always passes in Simply passing in |
@bradrobertson hm, and |
Sure... Ok so the story is:
Questions:
|
While Bunny supports its own ENV variable for URI connections IIRC (I have never advertised this feature and it was added for compatibility), Hutch's one is only managed by Hutch, so comma separating can be accomplished. "mq_api_host" is RabbitMQ HTTP API. I suspect that Ruby HTTP API client used by Hutch. Hutch uses it to infer some information about the topology. |
Err, by "can be accomplished" I mean "can be acceptable". I have no objections to that. |
Any updates on this? It is possible to pass in a connection as a workaround but this idea seems reasonable to me. |
Right now the connection_params enforces a singular
host
option for the Bunny connection. In an HA world we'd like this to be an array of rabbitmq hosts. Would you be open to allowing theuri
to have a comma separated host list, similar to how mongo handles clustering and instead passhosts
to Bunny?This would be a backwards compatible change.
The text was updated successfully, but these errors were encountered: