Is there some nice convenient way to check whether cookbook constraints can
be satisfied for a given runlist in a given environment?
I’m trying to add a lot of new constraints to an environment that has had
almost none for quite a while. At first I just added a simple constraint
for every cookbook to specify that each one must be the latest available
version, but I quickly found that made the dependencies unsolvable for some
runlists, as some cookbooks (eg. the nginx community cookbook) have
pessimistic version constraints.
I would like to check that the dependencies are solvable without having to
actually verify a real convergence on every single runlist (there are a lot
of them). Is there some easy way to exercise that dependency resolution
process on its own?
Harry Wilkinson | Manager, Cloud Engineering | Medidata Solutions
Metro Building, 1 Butterwick, Hammersmith, London W6 8DL
Twitter: @harwilk http://twitter.com/#!/harwilk
The information in this transmittal and any attachments are confidential
and intended only for the recipient(s) listed above.
You are hereby notified that any unauthorized distribution or copying of
this transmittal or its attachments is prohibited.
If you have received this transmittal in error, please notify the sender.