As a matter of fact, both of your suggestions are exactly how I deal with this situation. I find it less than ideal. Foregoing community cookbooks means not leveraging one of the strengths of chef. And having to have a different cookbook for each major language version is exactly the problem I was referring to. I hear you on the idempotency issue. It’s a lot more difficult to get idempotency with a file-editing approach. In a way, though, it may be a penny-wise, pound-foolish approach. Maybe it is better in the long run to implement idempotency for file edits, if it reduces the cookbook maintenance by such a large amount. From: Mathieu Martin [mailto:
Hey Kevin, Sam, If you need to change so few things, have you thought about skipping the community cookbooks? You could create much simpler cookbooks with as few tunable knobs as you need. In the case of php.ini, you can have one version of the cookbook per major language version. I agree it's not ideal development wise, but it makes idempotency simple and lets you have only one source of truth for your server configs. Mat
|
Archive powered by MHonArc 2.6.16.