This enhancement makes the plugin work in situations where node names, as registered with Consul, are not FQDN's but can be arbitrary unique strings (in my case it is EC2 "Name" tag which consists of environment, server role and instance id), and also where it is necessary to use long node names. .node.<consul_domain> is appended to the node names retrieved from Consul.
Originally I was going to enable this based on the value of RABBITMQ_USE_LONGNAME. However, as this would potentially break down in cases where nodes are registered in the catalog with their FQDN's (e.g. rabbit1.internal.domain would become rabbit1.internal.domain.node.consul), it seemed appropriate to introduce a separate flag to enable the feature.
ValFadeev
commented
7 years ago
This enhancement makes the plugin work in situations where node names, as registered with Consul, are not FQDN's but can be arbitrary unique strings (in my case it is EC2 "Name" tag which consists of environment, server role and instance id), and also where it is necessary to use long node names.
.node.<consul_domain>is appended to the node names retrieved from Consul.Originally I was going to enable this based on the value of
RABBITMQ_USE_LONGNAME. However, as this would potentially break down in cases where nodes are registered in the catalog with their FQDN's (e.g.rabbit1.internal.domainwould becomerabbit1.internal.domain.node.consul), it seemed appropriate to introduce a separate flag to enable the feature.