Issue #5259 has been updated by Felix Frank.
eric sorenson wrote:
> Feel free to reject this if it's unrelated, but this came up on the mailing
> list today - it would be great if, whatever the nomenclature ends up being (I
> like "title"), the value is accessible as a local variable inside a resource.
> I.e. this doesn't work, and it really ought to:
I disagree. Spawning a variable that is used in the scope of the resource
declaration, but is otherwise not defined in said scope, is bound to lead to
confusion and compatibility issues.
E.g. compatibility:
<pre>
# assuming $self is the new magic variable
class foo::bar {
$self = "i_break_future_versions_of_puppet.deb"
package { [ "foo", "bar" ]: source => "puppet:///modules/foo/packages/$self"
}
</pre>
----------------------------------------
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.
