[chef] Re: Re: Re: Re: Ideas for namespacing breaking attribute changes

[Cary Penniman < >]

On Thu, Jan 23, 2014 at 3:45 PM, Zac Stevens < " target="_blank"> > wrote:

I'm in favour of two versions of the cloud attributes existing side-by-side, the old one deprecated for a suitably long period before being removed. 

+1. 

As far as interval of time, since removing a plugin breaks backwards compatibility, IMHO, this should only be done on a major revision bump. As Bryan points out in the ticket [1], ohai is inherently linked to chef, so we would need to wait for a major bump of chef as well (i.e. v12). 

 

 

 The plugin could log a deprecation warning, but this doesn't help to identify anything using it...  Shipping Foodcritic rules to highlight deprecated usage would be a help.

+1 to the food critic rule idea. 

Proposal

-------------

Adopt a versioning syntax in the plugin namespace of "<plugin_name>[_vN]".  Where, "N" is the version of the plugin.  A version of "1" is implied if the "_vN" is omitted.  

For example:

node["cloud"] is v1 of the cloud plugin,

node["cloud_v2"] is v2 of the cloud plugin,

and so forth...

Given this syntax is should be fairly straightforward to write a foodcritic rule to report about the usage of deprecated namespaces.

But I am open to other ideas.

--

-Cary P

[1] https://tickets.opscode.com/browse/OHAI-542?focusedCommentId=46119&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-46119