The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #11730

document $module_name

Added by Garrett Honeycutt about 3 years ago. Updated over 1 year ago.

Status:ClosedStart date:01/04/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Keywords:module_name coupling Affected URL:
Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com


Description

$module_name is not documented. Suggest we add it to http://docs.puppetlabs.com/learning/variables.html


Related issues

Related to Puppet Documentation - Feature #11397: style guide should recommend that people use $module_name... Rejected 12/14/2011

History

#1 Updated by Cody Herriges about 3 years ago

To be more specific. Usage of $module_name and $caller_module_name should be more thoroughly explained as part of our documentation, beyond what is available at http://docs.puppetlabs.com/guides/faq.html. What affect does the caller_module_name variable have when it is defined or redefined as part of a override and does it have scoping implications, e.g. try inheriting a class vs. including it. If you include the variable is evaluated in the scope it is included in, if you inherit it is evaluated it in the scope it was defined. Same goes for module_name since it behaves differently, always being evaluated in the class it was defined.

#2 Updated by Nick Fagerlund over 1 year ago

  • Status changed from Unreviewed to Closed

It’s in the special variables section.

Also available in: Atom PDF