I am trying to build a packer build template that builds a windows server from an ISO and outputs a vagrant box. I have that part working the way that I want to using something similar to this:
{
“builders”: [
{
“type”: “virtualbox-iso”,
// …
}
],
“post-processors”: [
{
“keep_input_artifact”: false,
“output”: “./build/windows2019.box”
“type”: “vagrant”,
“vagrantfile_template”: “vagrantfile-windows.template”
}
]
}
The problem that I’m having is trying to additional post processing steps after this I keep getting remaining artifacts and I would like to remove these within the workflow and not have to hardcode in cleanup in my existing scripts.
Since my post processing scripts only need the path the the resulting box file, I figured just adding a manifest file would do the trick and then I could have the local shell post processor run my script to do the additional post processing but this still leaves me with files (*.ovf and *.vmdk files) in “output-virtualbox-iso” directory. Ive tried reading and understanding the artifice post processor but I don’t think I quite understand how to implement this correctly. Below is what I currently have.
{
"builders": [
{
"type": "virtualbox-iso",
// ...
}
],
"post-processors": [
{
"keep_input_artifact": false,
"output": "./build/windows2019.box"
"type": "vagrant",
"vagrantfile_template": "vagrantfile-windows.template"
},
{
"type": "manifest",
"output": "manifest.json"
},
{
"type": "artifice",
"keep_input_artifact": false,
"files":[
"./build/windows2019.box"
]
}
]
}
Any ideas what I might be doing wrong?