- From: Daniel DeLeo <
>
- To:
- Subject: [chef] Re: Re: Ideas for namespacing breaking attribute changes
- Date: Thu, 23 Jan 2014 13:25:19 -0800
On Thursday, January 23, 2014 at 1:16 PM, Matt Ray wrote:
I really like the configuration option of shipping both and specifying
the one to use. Default to the old plugin, but start throwing
deprecation warnings, and then drop the old plugin in the Ohai shipped
with Chef 12? That gives people plenty of time to upgrade without
breaking anything, knowing that Chef 12 clearly will break this.
The downside is that all cookbooks have to support both, or you have to upgrade everything in lockstep. You can’t have one cookbook that only supports v1 and another cookbook that only supports v2 in the same chef run.
Archive powered by MHonArc 2.6.16.