[chef] Peaceful Co-Existence of Multiple Versions of the Same Dependent Cookbook

[Stephen Corbesero < >]

I know that a multiple versions of the same cookbook can exist on a single chef server, but can different cookbooks depend on different versions of the same cookbook within an environment?

 

Suppose we have two “top level” cookbooks, “foo” and “bar” that share a dependency on a “common” cookbook, but at different versions: perhaps, “foo” depends on “common” at version “=1.2.3”, and  “bar” depends on “common” at  “~>2.0.0”

 

As long as “foo” and “bar” are not deployed on the same node, would all the nodes with the “foo” cookbook get the older version of the “common” cookbook, and would all the nodes with the “bar” cookbook get the latest version of “common” that was greater than 2.0.0?

 

I am not asking if this is a good thing to do.  I just want to know if different versions of the same cookbook could be deployed within an environment as long as they are on different nodes and the version constraints in the metadata have been correctly specified.

 

 

--

Stephen Corbesero, DevOps Engineer

Synchronoss - Mobile Innovation for a Connected World

Office: +1 484-821-4272

| www.synchronoss.com