Open boldandbusted opened 7 years ago
Hi there -- you're correct; elkstack specifically pins to an older elasticsearch cookbook:
depends 'elasticsearch', '~> 0.3.14' # 1.0 release is a radical change, needs work
So this is definitely never going to work until this cookbook is updated to work with the newer releases. I'd be glad to review / merge PRs, but I don't have an estimate for when to fix this right now. I'm focused on the upstream elasticsearch cookbook, which also has a bunch of updates to coincide with ES 5.0 being released.
@martinb3 Thank you. Is there any form of "rosetta stone" for converting configuration files between the versions? I'm actually just a dumb SysAdmin, not a "real" ElasticSearch/ELK "user". If the work is just boring tedious monkeywork, I'd be glad to help with a PR after testing.
@boldandbusted specifically for ES, they have an upgrading for each new version. For the elasticsearch cookbook, it's been converted to a library cookbook, so it's all Chef resources -- that would be the majority of the work in fixing elkstack (rewriting the recipe usage to be Chef resources instead). I don't have a ton of pointers beyond that -- but the tests in this cookbook should help be sure everything still works after moving to newer cookbook versions.
Howdy. I seem to have a problem isolated to elkstack here. Apologies in advance if I'm off the mark. :)
I'm using Chef-DK 0.19.6.
Berksfile:
This conflict doesn't occur when I comment out 'elkstack' in the Berksfile.
I'm happy to help with any further info. If I'm reading the above correctly, the conflict seems to be that elkstack wants an old version of ElasticSearch? And perhaps Kibana? Thanks in advance.