Hi,
I have a general question about parameter vs property. I always thought
that a property is something that can be insync or outofsync, so thats
something that puppet can check and correct.
But when I look at the current types, then target is always defined as
a property. So can target be
Hi,
I wanted to write a resourcetype to manage ports in /etc/services. I did
write a type where you can do something like:
port { 'telnet',
protocol = 'tcp',
number= '22',
port_aliases = ['alias1','alias2'],
}
This is totally sufficient for ME (I'm realising entries that just use
tcp,
As mentioned in the ticket it is not obvious that aliases do not belong
in the resourcename but have to be specified with the property
host_aliases. On the puppet-user list I saw someone using this as a
resource
@@sshkey {$fqdn,$hostname,$ipaddress:
type = rsa,
key = $sshrsakey,
}
On 21 November 2010 11:01, Stefan Schulte
stefan.schu...@taunusstein.net wrote:
Hi,
I wanted to write a resourcetype to manage ports in /etc/services. I did
write a type where you can do something like:
port { 'telnet',
protocol = 'tcp',
number = '22',
port_aliases =
