Issue #14985 has been updated by Andrew Parker.

Target version changed from 3.0.x to 3.x

As the 3.0.x line is winding down with the impending release of 3.1.0, I am 
removing the target at 3.0.x from tickets in the system and targeting them at 
3.x instead.
----------------------------------------
Bug #14985: calling_module and calling_class don't always return the calling 
module/class
https://projects.puppetlabs.com/issues/14985#change-80559

Author: Patrick Ramsey
Status: In Topic Branch Pending Review
Priority: Normal
Assignee: 
Category: 
Target version: 3.x
Affected Puppet version: 3.0.0
Keywords: hiera calling_class calling_module defined_type
Branch: https://github.com/puppetlabs/puppet/pull/1214


These two special hiera scope values are looked up by doing ".resource.name" on 
the Puppet::Parser::Scope from which hiera() was called, with the assumption 
that this will always return the class name.  However, if hiera() is called 
from within a define, then @real.resource will be an instance of that define, 
rather than of the class, and the value returned will be the name of that 
resource rather than of the class.

This is unintuitive (as it means calling_module/calling_class aren't set to a 
module or classname), and it breaks the ability to namespace against 
calling_class and title (to give specific resources their own configuration) a 
la

:hierarchy: - %{calling_class}/%{title}

I'll submit a patch later.  For now, I'm working around this by setting a 
constant inside my puppet define and matching against that in /etc/hiera.yaml, 
but that's kind of a hack.




-- 
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.

Reply via email to