[chef] Re: RE: Re: Trying to create links to installed package


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: RE: Re: Trying to create links to installed package
  • Date: Thu, 24 Oct 2013 09:21:06 -0700


On Monday, October 21, 2013 at 4:15 PM, THARP, JOSHUA L wrote:

Thank you for the help.

 

Is there a philosophical reason why specifying the version number is the better answer? Tying your recipe to a specific version of a package requires more maintenance. If Chef provided a way to detect the version number of the package it just installed, the recipe could be more generic.

If you specify the version number in the recipe, then all of your logic is in one place and you’re driving all of your configuration from one piece of data. This is easy to extend to a case where, say, you have multiple versions of the package in the repo and you want to try out the new version in a test/preprod/staging environment before you start using it in production.

In your current setup, you have moved some config info into your package repo, and it’s driven by logic you don’t control (namely, the sorting rules for package versions).

-- 
Daniel DeLeo




Archive powered by MHonArc 2.6.16.

§