On dependency:
My view is that many modules require you to install another module for
working (let's take concat for example).
I like as a module developer to release modules that "depend" on official
modules from puppetlabs if possible and if able to contribute to them
becouse there ale lots of different flavors and I think that a user could
be happyer to get just a single module and not a tree of dependant stuff so
... agree that user has to be avware that if he want to use the two modules
together he has to comply to a naming convention on data but no module
dependancy around.
But this is just my approach and very personal.
On the the hiera stuff I also vould like to have a hiera_hash_lookup where
the function behaves in a single shot getting the value fron the hash and
instead of returning it it looks-up for the value to the external lookpu.
Maybe it could be an idea for a feature enancement this way it could be
cleaner for user.
But in any way user will have to be instructed to create a hash in the yaml
file with the reference and the real value in the csv file so maybe the
fact of having the cose in the module is not a big problem user should just
"use" it is more a developer "cleaness need".
In any case I'll use that approach.
Obviously the security stuff can be a problem, I agree that you cannot
protect all, but a level of protection could be useful if there could be a
extlookup-gpg like there is a hiera-gpg maybe it could be nice.
Thanks
Luca
Il giorno mercoledì 28 agosto 2013 15:18:01 UTC+2, François Lafont ha
scritto:
>
> 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.
