We are using Chef 12 Enterprise, and have different organizations setup for development and QA.
We want to adapt to the Berkshelf way of managing cookbooks. The workflow puts a lot of emphasis on the “environment” cookbook, and I read numerous articles and watch numerous videos about it.
…and many more.
However, the concept of environment cookbook still eludes me. Can you please shed some light?
Say I have a product that has two VMs, a Web VM and a Router VM. Say I have the following cookbooks, (each cookbook is in its own repo and downloaded to the workstation)
My Web box needs these
My Router box needs these
I want to setup “dev” and “qa” environments so I can control the versions I want for all the above cookbooks in each environment.
Where does the environment cookbook come into play?
Should I have the following environment cookbooks (I inferred this from this link http://bytearrays.com/manage-chef-cookbooks-organization-repo) which says environment cookbooks " Represent a whole node to be installed/managed"
If so, what would above cookbook’s metadata.rb and Berkshelf.lock file look like?