Awesome!
I wonder about one other thing though, Is create_resources likely to balk if
there are values in the hash that are irrelevant for the resource type being
fed?
ie: if I have a region_repos hash that has both yum values, and apt values…
(assuming that a debian sibling to the yumrepo type comes along at some point
in the future) and feed them both via the same key, is that likely going to
cause me pain? or should the key be geared more to one or the other, i.e.:
region_yumrepo:
foo_repo: {
..
}
region_aptsource
foo_aptsource: {
…
}
just trying to think about where the pointy/sharp parts of this might be.
On Jun 13, 2012, at 8:24 AM, jcbollinger wrote:
>
>
> On Tuesday, June 12, 2012 5:51:06 PM UTC-5, Wolf Noble wrote:
> Hi John,
>
> Thanks a bunch. This seems incredibly sensible.
>
> If I'm understanding your suggestion properly, I interpret the best thing to
> do as something like:
>
>
> mymodule::repos {
> $region_repos = hiera('region_repos' , '' )
> $dc_repos = hiera('dc_repos' , '' )
>
> if $region_repos {
> create_resources('yumrepo', $region_repos))
> }
> if $dc_repos {
> create_resources('yumrepo', $dc_repos))
> }
> #...
> }
>
> and then I could override them like
>
> us-east/foo/qa/webservers/web02.qa.myfoo.com.yaml
>
> region_repos: ""
> dc_repos:
> foodc_qa_repo: {
> descr: foodc-qa,
> baseurl: http://myfoo.com/foodc-repo,
> gpgkey: http://myfoo.com/foodcrepo/key,
> gpgcheck: 1,
> enabled: 1,
> enablegroups: 0
> }
>
>
> with the known caveat that I'd have to explicitly redeclare the entire hash
> at the most relevant tier if I wanted to change any element of the hash
> already defined.
>
>
> Did I miss anything?
>
> I don't see any obvious errors or omissions. In particular, you are correct
> that overriding repos declared at a lower level will involve declaring an
> entirely new hash (of hashes) at the appropriate higher level. That's one of
> the costs attending complex data. All in all, it looks nicely fleshed out.
>
>
> John
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/Ts3RcypLci0J.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
________________________________
This message may contain confidential or privileged information. If you are not
the intended recipient, please advise us immediately and delete this message.
See http://www.datapipe.com/legal/email_disclaimer/ for further information on
confidentiality and the risks of non-secure electronic communication. If you
cannot access these links, please notify us by reply message and we will send
the contents to you.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
