berks apply command

[capoferro]

Addresses #440

This adds the berks apply ENVIRONMENT command to Berkshelf.

ALL version locks will be applied to the target environment's cookbook_versions hash

⚠️ Note that this does not address if cookbooks are being pulled from a path or git source. Perhaps this should error out if path or git cookbooks are detected?

[reset]

We should use Chef-Zero to handle these acceptance tests

[sethvargo]

So I really like this, but I think berks lock could be confusing to users. Someone might think it generates the lockfile, rather than applying the locked versions to an environment. What about berks apply?

[ivey]

Concur with @sethvargo on berks apply

[reset]

same here, I like berks apply

[reset]

@ivey @sethvargo @bluepojo updated to support the latest lockfile. Also modified the behavior slightly: the application of the lock will always include dependencies. From our architecture discussion the other day, this command makes most sense when you lock all dependencies to allow for some sort of "promotion" process across environments.

[capoferro]

Makes sense to me. I waffled a fair bit on whether to default to dependencies or not. I ended up choosing not to cause I imagined this feature would mimic what a human would do to lock their dependencies (that is: lock only the top level), but I see why locking dependencies by default is reasonable.

[capoferro]

👍

[sethvargo]

I'm 👍 on this now.