-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
Any provision to make it Chef 11.10 compatible? #401
Comments
Hi @sagar1730 -- chef 12.x was released about a year ago. We specifically dropped support for it when doing a 1.0.0 release, so I don't think we'd add it back in. It's a ton of additional testing, and in some cases, requires rewriting or maintaining a lot of legacy code. My recommendation would be to use an older version of this cookbook if you want to use Chef 11.x. I hope this helps! |
@sagar1730 - I strongly encourage you to contact your AWS account manager and complain about the state of OpsWorks. I've been howling about this for some time and haven't been getting anywhere. Getting some additional community members to chime in to AWS would be a big help. |
@sagar1730 - |
Sorry, that should be the 0.3.x branches, the last of which was https://github.com/elastic/cookbook-elasticsearch/tree/v0.3.14. |
Thanks @davidski ...I will test it now, I hope it will work. |
Hi,
I have tested it on Vagrant with Chef-Solo version 12.5 where it works perfectly, but when I tried it on AWS Opswork it failed. AWS supports only upto 11.10 for Linux and 12.1 for Windows. Is there any trick to make it Chef 11.10 compatible.
The text was updated successfully, but these errors were encountered: