-
Notifications
You must be signed in to change notification settings - Fork 127
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
Elasticsearch autodiscovery decisions in role #165
Comments
Also, FWIW, allowing users to also configure:
Would also be helpful. |
We can change the default value. Would that be here and here? graylog-ansible-role/defaults/main.yml Line 59 in d4673da
For the other configs, are these Graylog settings or Elasticsearch settings? We are just including the official Elasticsearch role in our code. So any settings available through that role should work: graylog-ansible-role/meta/main.yml Lines 8 to 10 in 22a004d
For additional graylog configs, we provide this setting. It allows users to pass any additonal Graylog configs needed.
|
Ah. Yeah, so those are Graylog config options if the additional config param can hold those, maybe we just need a readme update? |
@asachs01 I set |
@juju2112 there's probably a better title for this, but it arises out of some issues in z-#4632. The crux of it is that the role is being used with commercially packaged Elasticsearch and does some things that lead to confusion when using the role with that version of ES--those are:
Would it be worth changing 1. so that the default behavior is to not enable autodiscovery and can we make it possible so that folks using the role can enable
elasticsearch_discovery_default_scheme
?The text was updated successfully, but these errors were encountered: