Issue #8096 has been reported by Nick Fagerlund.
----------------------------------------
Bug #8096: Shouldn't be able to declare both "name" and namevar for types that
have namevars
https://projects.puppetlabs.com/issues/8096
Author: Nick Fagerlund
Status: Accepted
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
These both work:
file {'myfile':
ensure => file,
content => "hi there",
path => "/tmp/pathfile",
name => "/tmp/namefile",
}
exec {'myexec':
logoutput => true,
command => '/opt/local/bin/cowsay "from command"',
name => '/opt/local/bin/cowsay "from name"',
}
Luke informed us that this used to throw an exception, though I haven't tested
to find out which versions that applies to.
Nigel and I think "name" just shouldn't be allowed if there's a declared
namevar like "path;" it's not introspectible, and amounts to a secret backdoor
that leads to illegible Puppet code. Luke said he doesn't have a philosophical
problem with doing that, but he believes we should do a real deprecation
instead of silently fixing it, since it's a change in behavior that might cause
some unknown amount of havoc out in the wild.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
