-
Notifications
You must be signed in to change notification settings - Fork 53
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
normal vs default attribute #171
Comments
Yes, at the time it was due to the upstream cookbook. |
There's some major releases pending in elasticsearch (the cookbook) tied to v2.0.0 of Elasticsearch (the software project), but then I'd like to do a big refactor of elkstack to catch it up to the new versions. |
That sounds great. I'd be interested in assisting (especially with the logstash integration) as we use this cookbook pretty extensively in our setup. |
@phoolish That would be wonderful! Honestly, we could start any time. |
I think we're looking at: So I'm thinking we'd bump to those, and then refactor. |
That makes sense. Could you also elaborate on #136? |
@phoolish I tried to update that. At it's core, it's basically "refactor" so we are doing the interesting work around E, L, and K but not necessarily write custom implementations of things like SSL certificates. |
Seems like the right approach. I'll get started tomorrow. |
Why is a normal attribute used vs a default attribute on https://github.com/rackspace-cookbooks/elkstack/blob/master/attributes/logstash.rb#L2 ? Is this due to an upstream cookbook?
The text was updated successfully, but these errors were encountered: