On 17.12.2009 18:55, Michael Gliwinski wrote:
>> This define can be used in a class like
>> class ssh::eal4 {
>>
>> # Cripto settings
>> ssh::config { Protocol:
>> value => "2",
>> }
>>
>> ssh::config { Ciphers:
>> value => "3des-cbc",
>> }
>>
>> # X11 forwarding (You MAY allow)
>> ssh::config { X11Forwarding:
>> value => "no",
>> }
>> [....]
>> }
>
> This makes sense, one problem with that however is that this creates a
> resource for each option. So AFAIK for augeas that means the code (opening
> the file, trying and appying changes) will be executed as many times as you
> have options.
>
> Perhaps when hashes are available using them to map (key, value) pairs to
> augeas set commands would make sense.
If there is a performance problem augeas[1] needs to learn batching.
Resources and defines are already hashes. Using another layer of hashes
on top of hashes to work around an implementation detail is just awful.
Regards, DavidS
[1] and package providers and everybody else. This was already discussed
a few months ago. Doing it right requires a major restructuring of the
puppet executor but will bring benefits without compromising puppet's
datamodel
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
