--- description: | All strings within templates are processed by a common Packer templating engine, where variables and functions can be used to modify the value of a configuration parameter at runtime. layout: docs page_title: Configuration Templates ... # Configuration Templates All strings within templates are processed by a common Packer templating engine, where variables and functions can be used to modify the value of a configuration parameter at runtime. For example, the `{{timestamp}}` function can be used in any string to generate the current timestamp. This is useful for configurations that require unique keys, such as AMI names. By setting the AMI name to something like `My Packer AMI {{timestamp}}`, the AMI name will be unique down to the second. If you need greater than one second granularity, you should use `{{uuid}}`, as when you have multiple builders in the same template. In addition to globally available functions like timestamp shown before, some configurations have special local variables that are available only for that configuration. These are recognizable because they're prefixed by a period, such as `{{.Name}}`. The complete syntax is covered in the next section, followed by a reference of globally available functions. ## Syntax The syntax of templates is extremely simple. Anything template related happens within double-braces: `{{ }}`. Variables are prefixed with a period and capitalized, such as `{{.Variable}}` and functions are just directly within the braces, such as `{{timestamp}}`. Here is an example from the VMware VMX template that shows configuration templates in action: ``` {.liquid} .encoding = "UTF-8" displayName = "{{ .Name }}" guestOS = "{{ .GuestOS }}" ``` In this case, the "Name" and "GuestOS" variables will be replaced, potentially resulting in a VMX that looks like this: ``` {.liquid} .encoding = "UTF-8" displayName = "packer" guestOS = "otherlinux" ``` ## Global Functions While some configuration settings have local variables specific to only that configuration, a set of functions are available globally for use in *any string* in Packer templates. These are listed below for reference. - `build_name` - The name of the build being run. - `build_type` - The type of the builder being used currently. - `isotime [FORMAT]` - UTC time, which can be [formatted](https://golang.org/pkg/time/#example_Time_Format). See more examples below. - `lower` - Lowercases the string. - `pwd` - The working directory while executing Packer. - `template_dir` - The directory to the template for the build. - `timestamp` - The current Unix timestamp in UTC. - `uuid` - Returns a random UUID. - `upper` - Uppercases the string. ### isotime Format Formatting for the function `isotime` uses the magic reference date **Mon Jan 2 15:04:05 -0700 MST 2006**, which breaks down to the following:
Day of Week | Month | Date | Hour | Minute | Second | Year | Timezone | |
---|---|---|---|---|---|---|---|---|
Numeric | - | 01 | 02 | 03 (15) | 04 | 05 | 06 | -0700 |
Textual | Monday (Mon) | January (Jan) | - | - | - | - | - | MST |