Ive used Chef for a while but mainly focused on individual projects. We would wrap a community cookbook for our project and move on. All was right with the world.
However, now I am in a position where we may want to write wrapper cookbooks for the company as a whole. But was wondering if that was going to bring an extra layer of chaos and dependency into the mix.
For example if I wanted to write a company wide Apache cookbook wrapper for Apache2, then someone wants to wrap my company cookbook. Is that going to cause problems? Doesnt Berks get upset with a dependency that deep? Am i introducing chaos?
Our thought was to have a base level cookbook teams could use that set company standards on a community coobook, then they wrap our cookbook.
Everything I have read up on is totally in favor of wrappers, but what about wrapping the wrappers?
This is a diagram of what I am talking back:
Community Cookbook <- Company Cookbook <- Project Cookbook