If possible, you should structure your recipes and roles to avoid this situation entirely. If that's not an option, you can use `include_attribute` in an attributes file to force one attributes file to load before another.On Wednesday, August 10, 2011 at 6:15 PM, Joaquin Casares wrote:
> Hello,
> I have cookbook X that calls many functions off of cookbook Y. But my attributes for cookbook X are a superset of cookbook Y's attributes and of the values that intersect some are different in cookbook X.
> How would I go about doing this correctly?
> Right now I call include_recipe "Y::recipe1" from "X::default", but it seems to overwrite all my X configs that intersect.
> Should I just change cookbook X to use override instead of default settings?
> Thanks for the help!
> Joaquin
--
Dan DeLeo
Archive powered by MHonArc 2.6.16.