Skip to content
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

Document requirement on Chef 12+ #338

Closed
davidski opened this issue Jul 9, 2015 · 2 comments
Closed

Document requirement on Chef 12+ #338

davidski opened this issue Jul 9, 2015 · 2 comments
Assignees

Comments

@davidski
Copy link

davidski commented Jul 9, 2015

The rewrite to use poise2 means that this cookbook now has a requirement on Chef 12+. Not usually a problem except for us poor souls trying to run this on AWS OpsWorks, which is currently stuck on Chef 11. :sad: Adding an issue to provide a search hit for anyone else trying to use the rewritten cookbooks on AWS.

@martinb3
Copy link
Contributor

martinb3 commented Jul 9, 2015

@davidski if the previous releases (the 0.x branch) work for you, those are definitely still available. For what it's worth, there's a branch in place that removes poise, but it significantly increases the verbosity of what's in the libraries. I'm not sure if it's worth merging yet.

@martinb3 martinb3 self-assigned this Jul 9, 2015
@martinb3 martinb3 added the doc label Jul 9, 2015
@davidski
Copy link
Author

davidski commented Jul 9, 2015

Thanks, @martinb3! I'm still happily using the 0.3.x branch. I just wanted to play with the new rewrite. I totally understand the dependency on poise and Chef12. Other community cookbooks, such as the Kibana cookbook, are starting to become Chef12 dependent. This is completely an AWS problem. Of course, a doc note would be spiffy. 😄

@martinb3 martinb3 added this to the 1.0.0 release to Supermarket milestone Jul 16, 2015
martinb3 added a commit that referenced this issue Jul 16, 2015
- Add note about chef 12 and standards
- Document configure, service, and plugin resources

Fixes #338.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants