On Monday, 28 April 2014 20:55:30 UTC+12, Felix.Frank wrote:
>
> Hi, 
>
> this is really, really meta (http://xkcd.com/917/). 
>

Nevertheless, I nailed it?
 

> I'm a little cautious of building something like this: 
> http://thedailywtf.com/Articles/The_Enterprise_Rules_Engine.aspx 
>

Oh, come on. If you didn't like domain specific languages you'd be avoiding 
this puppet manifest muck and use Chef, instead. The point of them, and 
configuration files to some extent, is to achieve greater brevity, safety 
and maintainability than a general purpose language. They only turn into 
Enterprise Rules Engines when the result is a verbose, obfuscated, mess.
 

> I'd have to play with your module though in order to get a feel about 
> wether it is rather useful or over the top. 
>

With this, I get to separate resource configuration data from manifest code 
by writing short, pithy YAML, so I think I'm winning.

And admittedly, I could have called it something like resource_map and made 
the primary hiera data a simple mapping of resource types to keys, rather 
than the more recursive and distastefully named solution I've published, 
but kind of the point is, shouldn't there be an easier way? Baked into the 
hiera/puppet bindings?

One remark about your README - it's true that the adoption of functions 
> is not mentioned in the current documentation, but please note that you 
> can trace past documentations and easily bisect the origin of any 
> specific feature: 
>
> http://docs.puppetlabs.com/references/3.2.2/function.html 
> http://docs.puppetlabs.com/references/2.7.20/function.html 
> etc. 
>
> Also, git. :-) 
>

Right now, having documentation at all puts me head and shoulders above the 
long tail of Puppet Forge module authors. Now I guess I could be motivated 
to go through the last half dozen references and annotate the functions 
with version introductions, and changes, but only if I believed the pull 
request would be accepted, and the trend continued.

John 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ce455318-90da-488d-aaae-c62b817daa9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to