[chef] Re: Redhat admins, if a cookbook enables EPEL, is that a surprise?

[Jesse Campbell < >]

I suppose I'm going against the grain here, but in our house I wrote a different recipe yum::attribute_hash that parses a hash from attributes to generate all of the .repo files, rather than having a separate recipe for each one. This allows us to be consistent in placing the repo url locations into our different environment files.

the hash looks like this:
  :repo => {
    :list => {
      "CentOS-Base" => {
        :url =">" "http://yum-web.internal:8080/CentOS/$releasever/os/$basearch/",

        :enabled => true
      }
    }
  }

Anything that isn't in the list gets wiped out by the recipe, so someone adding yum::epel to a recipe would cause chef to create the epel .repo file, flush the yum cache, then wipe it out again and re-flush the cache, for every run (unless it was *also* added to the attribute hash).

Not exactly ideal.

I can post the recipe for those interested.

-Jesse

On Fri, Nov 16, 2012 at 4:29 PM, Bryan McLellan < " target="_blank"> > wrote:

Would you be surprised if you ran a community cookbook for a piece of
software and it configured EPEL to do so?

It seems like getting most things done requires it, but we haven't made a
global pattern yet to override the use of EPEL yet.

If everyone just uses EPEL, then it is a moot point.

---
Bryan McLellan | opscode | technical program manager, open source
(c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org