We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using node.elasticsearch[:custom_config][:network.host] to have Elasticsearch bind to a specific IP (which is not 127.0.0.1). This works great, but the proxy recipe fails because it has localhost hardcoded (https://github.com/elasticsearch/cookbook-elasticsearch/blob/master/templates/default/elasticsearch_proxy.conf.erb#L26, https://github.com/elasticsearch/cookbook-elasticsearch/blob/master/templates/default/elasticsearch_proxy.conf.erb#L50). Instead it should use
node.elasticsearch[:custom_config][:network.host]
<%= node.elasticsearch[:custom_config][:network.host] || node.elasticsearch[:custom_config][:network.bind_host] || 'localhost' %>
(or something like that).
The text was updated successfully, but these errors were encountered:
Hey, understood.
First, you can just set node.network.host, you shouldn't be forced to use the custom_config namespace.
node.network.host
custom_config
I'll test the suggestion in Vagrant and verify it.
Sorry, something went wrong.
07adcf5
Thanks!, implemented and verified. Please check out if this works for you.
No branches or pull requests
I'm using
node.elasticsearch[:custom_config][:network.host]
to have Elasticsearch bind to a specific IP (which is not 127.0.0.1). This works great, but the proxy recipe fails because it has localhost hardcoded (https://github.com/elasticsearch/cookbook-elasticsearch/blob/master/templates/default/elasticsearch_proxy.conf.erb#L26, https://github.com/elasticsearch/cookbook-elasticsearch/blob/master/templates/default/elasticsearch_proxy.conf.erb#L50). Instead it should use(or something like that).
The text was updated successfully, but these errors were encountered: