Hi all,
I suppose most of you have read R.I.Pienaar's blog post about his 
module_data module:
http://www.devco.net/archives/2013/12/08/better-puppet-modules-using-hiera-data.php?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+planetpuppet+%28Planet+Puppet%29

I've played a bit with it still haven't found any issue.
It's very easy and straightforward to implement (let's be honest, ARM-9 
approach was not as plainly easy)
This commit shows how quickly a module can be 
converted: http://bit.ly/18K6dSY

But the real advantage, at least for me, is not for such a common case 
(where params.pp may not be elegant but does what's needed), but a case 
where some values which typically go in params.pp may change not according 
to the os but according to parameters passed to the module, such as 
installation method or version.

In such a case I found this approach really a killer.
An example is here: http://bit.ly/1gCkQQ8 
To manage a similar case (Postgres' params when you want to use the 
official postgres.org repos) in a normal way would require a lot of extra 
code which can't even stay in params.pp.
A hierarchy that looks like:

---
 :hierarchy:
   - "install_class/%{install_class}" 
   - "operatingsystem/%{::operatingsystem}-%{::operatingsystemrelease}"
   - "operatingsystem/%{::operatingsystem}"
   - common
is enough to cover most of the weirdest cases where I wanted to provide modules 
with alternative install options.


So, my point is:
if it's true (that's how I've understood) that the data in module solution 
introduced in 3.3.0 has been held back, is there any chance that this one might 
be introduced into core Puppet?

And, in any case, what's the current plan for Data in modules? 

Best *
Al

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/4b9fa326-03e8-4a15-b4c6-48e6432044c0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to