summaryrefslogtreecommitdiffstats
path: root/lib/puppet/util/rdoc/code_objects.rb
diff options
context:
space:
mode:
authorStefan Schulte <stefan.schulte@taunusstein.net>2010-11-21 20:52:49 +0100
committerNick Lewis <nick@puppetlabs.com>2010-11-30 16:17:19 -0800
commit0ab5e0f779d7261c4a9faf890cef8df52726a82a (patch)
treeea38e57b7665a65854e555f4d3367eeebf653bb0 /lib/puppet/util/rdoc/code_objects.rb
parent701021f97870b4b0be07440b30a5c53faaf39933 (diff)
downloadpuppet-0ab5e0f779d7261c4a9faf890cef8df52726a82a.tar.gz
puppet-0ab5e0f779d7261c4a9faf890cef8df52726a82a.tar.xz
puppet-0ab5e0f779d7261c4a9faf890cef8df52726a82a.zip
(#2495) Better value validation for sshkey
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, } Puppet will now write a correct entry to the know_hosts file, but when it rereads the file, the field $fqdn,$hostname,$ipaddress is split into name ($fqdn) and host_aliases ([$hostname,$ipaddress]). Since we dont find the resource the user specified, puppet will put the same key in the file over and over again. This patch adds a simple validation on resourcename.
Diffstat (limited to 'lib/puppet/util/rdoc/code_objects.rb')
0 files changed, 0 insertions, 0 deletions