Skip to content
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

Support hostname from nodename in consul using CONSUL_SVC_ADDR_NODENAME #4

Merged
merged 2 commits into from
Mar 20, 2017

Conversation

dcorbacho
Copy link

Adresses user request to select the long nodename given instead of
retrieving it from inets.

[#141944663]
aweber#62

Adresses user request to select the long nodename given instead of
retrieving it from inets.

[#141944663]
aweber#62
@@ -35,6 +35,7 @@
{config, consul_svc_addr, "CONSUL_SVC_ADDR", "undefined", string, false},
{config, consul_svc_addr_auto, "CONSUL_SVC_ADDR_AUTO", false, atom, false},
{config, consul_svc_addr_nic, "CONSUL_SVC_ADDR_NIC", "undefined", string, false},
{config, consul_svc_addr_nodename, "CONSUL_SVC_ADDR_NODENAME", false, atom, false},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we have USE_LONGNAME can we use directly it without add another variable ? CONSUL_SVC_ADDR_NODENAME, WDYT?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it would change the actual behaviour. In this case, it is optional and only interested users need to configure it.

@Gsantomaggio
Copy link
Member

LGTM!

@michaelklishin michaelklishin merged commit 1017a7a into stable Mar 20, 2017
@dumbbell dumbbell deleted the rabbitmq-autocluster-62 branch January 2, 2018 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants