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.
31 lines
507 B
HCL
31 lines
507 B
HCL
source "file" "chocolate" {
|
|
content = "chocolate"
|
|
target = "chocolate.txt"
|
|
}
|
|
source "file" "vanilla" {
|
|
content = "vanilla"
|
|
}
|
|
|
|
build {
|
|
sources = [
|
|
"source.file.chocolate",
|
|
"source.file.vanilla"
|
|
]
|
|
|
|
post-processors {
|
|
post-processor "shell-local" {
|
|
name = "apple"
|
|
inline = [ "echo apple 'apple'" ]
|
|
}
|
|
|
|
post-processor "shell-local" {
|
|
name = "pear"
|
|
inline = [ "echo apple 'pear'" ]
|
|
}
|
|
|
|
post-processor "shell-local" {
|
|
name = "banana"
|
|
}
|
|
}
|
|
}
|