Issue #5259 has been updated by Felix Frank.
> That said, I *really* think it would be worth the pain and suffering to
> change that now and have $name be "the current resource" rather than "the
> enclosing define", since that is considerably more commonly used.
As in
<pre>
define foo() {
file { "/tmp/$name": mode => 644 }
class { "bar": file => $name }
}
</pre>
Leading to bar using "bar" for the "file" parameter? Wouldn't that break almost
each last define out there that does more than encapsulate a single resource?
----------------------------------------
Bug #5259: Synonyms (title, namevar, name) make it confusing.
https://projects.puppetlabs.com/issues/5259
Author: Jordan Sissel
Status: Accepted
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords: consistency usability
Branch:
* If you're querying a resource, it's Someresource <| title == ... |>
* If you're writing a provider, it's called a 'namevar'
* If you're implementing a custom define, it's called $name.
This is confusing and could benefit from unification, even if it's a small step
such as unifying $name and title.
--
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.
