Le 28/08/2013 11:57, Luca Gioppo a écrit :
It seems a very clever approach!!!

Are you talking about the "extlookup" approach?

There is one thing which toubles me with extlookup. For me, when I put:

    $snmp      = hiera_hash('snmp')
    $community = extlookup($snmp['community'])

instead of :

    $snmp      = hiera_hash('snmp')
    $community = $snmp['community']


I show an implementation detail ("the data is not in a yaml file but in a external source") which should not be appear in the module. In fact, I would like to have a new "hiera_hash"function which behaves exactly like the current "hiera_hash" function (in Puppet 3), except when a value matchs this regex /^extkey_/ (by example) where, in this case, the function apply automatically extlookup("the-value") in a transparent way for the user.

If it works could be the approach for not having dependency.
I do not agree that the two module are dependend, they just depend on the same data, but given the data should be able to work on their own.

Ok, the data are dependent, not the modules. Why not.

could the data be protected in some way? just not to have maby common password written in clear?

This is another question. Personally, I have no solution, but it's a interesting question.

--
François Lafont

--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to