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
It seems that the generated logstash configs are always generated with the pillar input being put into strings ("").
For example
outputs: - plugin_name: elasticsearch cond: 'if [type] == "test"' workers: 8 index: 'test-%{+YYYY.MM.dd}' flush_size: 5000 hosts: - 127.0.0.1:9200
Is parsed into:
output { if [type] == "test" { elasticsearch { index => "test-%{+YYYY.MM.dd}" workers => "8" hosts => [ "127.0.0.1:9200" ] flush_size => "5000" } } }
In this case logstash will fail overwriting the default of the "workers" setting:
:message=>"Pipeline aborted due to error", :exception=>#<ArgumentError: comparison of String with 1 failed>
This is on logstash-2.3.3; I don't know if logstash previously has been able to overwrite int setting inputs with string.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It seems that the generated logstash configs are always generated with the pillar input being put into strings ("").
For example
Is parsed into:
In this case logstash will fail overwriting the default of the "workers" setting:
:message=>"Pipeline aborted due to error", :exception=>#<ArgumentError: comparison of String with 1 failed>
This is on logstash-2.3.3; I don't know if logstash previously has been able to overwrite int setting inputs with string.
The text was updated successfully, but these errors were encountered: