-
Notifications
You must be signed in to change notification settings - Fork 22
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
Chef 12? #11
Comments
I have not tried out Chef 12. As it seems to forgo the built-in opsworks cookbooks and make some substantial changes to the provisioning process, I'd like to do a bit of testing before I throw this in here. May have to create a new branch for Chef 12 support in case others wish to remain on Chef 11.xx. |
Having looked at Chef 12 now, I'm not sure how useful a VM image would be at this point. The OpsWorks cookbooks are now run completely isolated from custom cookbooks and have very few side effects to account for. For 98% of cases, I suspect using Vagrant with it's basic Chef plugin would suffice to test OpsWorks Chef 12 stacks. I'm open to the idea of updating this Packer vm if there's enough of a demand though... Anyone have any thoughts or want to weigh in? |
@mikegreiling I would definitely be interested in your thoughts on this. I'm unsure of the best way to go about testing opsworks-based stacks in a local vagrant VM using Chef 12 and custom json from opsworks. Happy to collaborate/help if possible! |
Hey @jpooler sorry for the really late response. I don't have any plans to update this to work with Chef 12, but if you or anybody else wants to take over and work on this I'd be happy to hand over the project. My company is migrating from Chef + OpsWorks to a Docker-based platform, so I don't think I'll have the time or motivation to continue updating this repo. |
Opsworks now support chef 12
http://docs.aws.amazon.com/opsworks/latest/userguide/chef-12-linux.html
The text was updated successfully, but these errors were encountered: