Several words in the Puppet language are reserved. This means they:
The following words are reserved:
and— expression operator
application— reserved for future use; logs warning instead of error
attr— reserved for future use
case— language keyword
class— language keyword
consumes— reserved for future use; logs warning instead of error
default— language keyword
define— language keyword
else— language keyword
elsif— language keyword
false— boolean value
function— reserved for future use
if— language keyword
import— former language keyword (now removed)
in— expression operator
inherits— language keyword
node— language keyword
or— expression operator
private— reserved for future use
produces— reserved for future use; logs warning instead of error
true— boolean value
type— reserved for future use
undef— special value
unless— language keyword
Integer[title], you would have to use
The following are built-in namespaces used by Puppet and so must not be used as class names:
main— Puppet automatically creates a
mainclass, which contains any resources not contained by any other class.
settings— The automatically created
settingsnamespace contains variables with the settings available to the compiler (that is, the Puppet master’s settings).
Additionally, the names of data types can’t be used as class names:
The following variable names are reserved, and you must not assign values to them:
$0— These regex capture variables are automatically set by regular expressions used in conditional statements, and their values do not persist outside their associated code block or selector value. Puppet will raise an error if you try to assign to these variables.
$factsvariables are reserved for facts and cannot be reassigned at local scopes.
The following are special variable names that may not be used as parameters in classes or defined types:
$title– the title of a class or defined type
$name– a synonym for
Puppet limits the characters you can use when naming language constructs.
Note: In some cases, names containing unsupported characters will still work. These cases should be considered bugs, and may cease to work at any time. Removal of these bug cases will not be limited to major releases.
Variable names begin with a
$ (dollar sign) and are case-sensitive.
Most variable names must start with a lowercase letter or an underscore. The exception is regex capture variables, which are named with only numbers.
Variable names can include:
If the first character is an underscore, that variable should only be accessed from its own local scope; using qualified variable names where any namespace segment begins with
_ is deprecated.
Note that some variable names are reserved.
Qualified variable names are prefixed with the name of their scope and the
:: (double colon) namespace separator. (For example, the
$vhostdir variable from the
apache::params class would be
Optionally, the name of the very first namespace may be empty, representing the top namespace. In previous versions of the Puppet language, this was often used to work around bugs, but it’s not necessary in this version. The main use is to indicate to readers that you’re accessing a top-scope variable, e.g.
Short variable names should match the following regular expression:
Qualified variable names should match the following regular expression:
The names of classes and defined types can consist of one or more namespace segments. Each namespace segment must begin with a lowercase letter and can include:
Namespace segments should match the following regular expression:
The one exception is the top namespace, whose name is the empty string.
Multiple namespace segments can be joined together in a class or defined type name with the
:: (double colon) namespace separator.
Class names with multiple namespaces should match the following regular expression:
Additionally, you cannot use the name
<MODULE NAME>::init for a class or defined type. This is because
init.pp is a reserved filename, which should contain a class named after the module.
Module names obey the same rules as individual namespace segments (like in a class or defined type name). That is, they must begin with a lowercase letter and can include:
Module names should match the following regular expression:
Class and defined type parameters begin with a
$ (dollar sign), and their first non-
$ character must be a lowercase letter. They can include:
Parameter names should match the following regular expression:
Tags must begin with a lowercase letter, number, or underscore, and can include:
Tag names should match the following regular expression:
Resource titles can contain any characters whatsoever. They are case-sensitive.
Resource names (or namevars) might be limited by the underlying system being managed. (E.g., most systems have limits on the characters allowed in the name of a user account.) The user is generally responsible for knowing the name limits on the platforms they manage.
The set of characters allowed in node names is undefined in this version of Puppet. For best future compatibility, you should limit node names to letters, digits, periods, underscores, and dashes. (That is, node names should match
Environment names can contain lowercase letters, numbers, and underscores. That is, they must match the following regular expression: