- From: Peter Donald <
>
- To: Chef Mailing List <
>
- Subject: [chef] Re: Re: What to pin in environments?
- Date: Wed, 29 Jan 2014 16:02:11 +1100
>
And no, it's not that easy anymore to see which versions of the apache
>
cookbook are in use anymore (well it might be searchable via the chef server
>
API?)
We use a variant of knife-audit [1] to do this for us and it works well.
>
To me it seems that many people take the route of pinning everything in the
>
environment (e.g. via `berks apply`). To me it seems wrong (or at least as a
>
smell) to use environments for that, but that's just my view and there might
>
be some good reasons to do it the other way around. This is just what works
>
well for me...
I would really like to use the technique you use and we did actually
migrate towards the approach of only locking down top-level cookbooks
in the environment files and then lock down supporting cookbooks in
the top-level cookbooks metadata.
Unfortunately we repeatedly ran in to the dependency resolver bug in
Chef 11 (CHEF-3921) which would kill our chef server. So we were
forced back to locking down everything in environments.
[1]
https://github.com/jbz/knife-audit
--
Cheers,
Peter Donald
Archive powered by MHonArc 2.6.16.