So basically I am using this (http://github.com/larstobi/puppet-dns/)
module to manage amazon's route53 dns entries.
The generic definition goes like that:
node 'testnode' {
base::route53::r53delegation { "$primary_fqdn.": ;}
}
On a server node which (is actually my puppet master) submit
I am doing something like that:
class users::userlist {
@users::virtual::localuser { "ubuntu":
sshkey => {
'test_key' => { key => 'XX' },
'test_key2' => { key => 'YY'},
,}
groups => 'test_group',
}
}
All is good whenever I just
do
Class['base::route53::r53server']
}
Anyway, that is not that important although a bit annoyingI hope in 3.x
this will be fixed, time to put some effort to migrate anyway.
On Thursday, 25 October 2012 14:58:34 UTC+1, jcbollinger wrote:
>
>
>
> On Wednesday, October 24, 201
4, 2013 9:20:23 AM UTC-6, MCZ wrote:
>>
>> Its puppet 2.7.x latest, I chain resources like this:
>>
>> node 'puppetmaster-client' {
>> include base::route53::r53server
>> $primary_fqdn = 'puppetmaster.foo.bar'
>>
So I am looking at https://github.com/puppetlabs/puppetlabs-stdlib which
states module version is 4.1.0 and it has a bunch of new functions that do
not exist in the forge version of the module version 4.1.0, like:
# stdlib/lib/puppet/parser/functions/deep_merge.rb
# stdlib/lib/puppet/parser
