Writing Packer Templates: Difference between revisions
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
=Internal= | =Internal= | ||
* [[Packer_Concepts#Writing_Templates|Packer Concepts]] | * [[Packer_Concepts#Writing_Templates|Packer Concepts]] | ||
=Template Structure= | |||
<syntaxhighlight lang='groovy'> | |||
packer { | |||
} | |||
source { | |||
} | |||
build { | |||
} | |||
</syntaxhighlight> | |||
=Template User Variables= | =Template User Variables= |
Revision as of 01:30, 4 June 2021
External
- https://learn.hashicorp.com/tutorials/packer/docker-get-started-build-image#write-packer-template
- https://www.packer.io/docs/templates/engine.html
Internal
Template Structure
packer {
}
source {
}
build {
}
Template User Variables
Template Variables
Template variables are special variables automatically set by Packer at build time. Some builders, provisioners and other components have template variables that are available only for that component. Template variables are recognizable because they're prefixed by a period, such as {{ .Name }}
. For example, when using the shell provisioner template variables are available to customize the execute_command
parameter used to determine how Packer will run the shell command:
{
"provisioners": [
{
"type": "shell",
"execute_command": "{{.Vars}} sudo -E -S bash '{{.Path}}'",
"scripts": [
"scripts/bootstrap.sh"
]
}
]
}
.Vars
The {{ .Vars }}
template variable is replaced with the list of environment variables, if configured as environment_vars
.
.Path
The {{ .Path }}
template variable is replaced with the path of the script to be executed.
.EnvVarFile
Examples
Amazon EBS Template Example
A simple template that produces an Amazon AMI
{
}