c7b35dd6bc
added `post-processors` block to run chained post-processors after a build. Before this, defining multiple `post-processor` blocks after provisioning steps would run them sequentially, now doing this makes them start from the build's artifact. To queue post-processors you now have to define them in a `post-processors` block. This is a breaking change.
40 lines
657 B
HCL
40 lines
657 B
HCL
|
|
|
|
build {
|
|
name = "aws_example_builder"
|
|
description = <<EOF
|
|
The builder of clouds !!
|
|
|
|
Use it at will.
|
|
EOF
|
|
|
|
sources = [
|
|
"source.amazon-ebs.example-1",
|
|
|
|
// this one is not defined but we don't want to error there, we just
|
|
// would like to show what sources are being referenced.
|
|
"source.amazon-ebs.example-2",
|
|
]
|
|
|
|
provisioner "shell" {
|
|
files = [
|
|
"bins/install-this.sh",
|
|
"bins/install-that.sh",
|
|
"bins/conf-this.sh",
|
|
]
|
|
}
|
|
|
|
post-processor "manifest" {
|
|
}
|
|
|
|
post-processor "shell-local" {
|
|
}
|
|
|
|
post-processors {
|
|
post-processor "manifest" {
|
|
}
|
|
|
|
post-processor "shell-local" {
|
|
}
|
|
}
|
|
} |