When this post processor is used with artifacts from the 'artifice' post processor along with the provider_override="hyperv", the resulting .box output file does not seem to be valid.
Reproduction Steps
Prerequisite:
following Hyper V vm source files :
packer with the necessary plugins installed
Execute : packer build
Expected behaviour: a working vagrant box (.box file) is generated from the hyperv source files
Observed behaviour:
An incomplete .box file file is generated (see attached file:packer_example_hyperv_amd64.box in the zip file ).
packer_example_hyperv_amd64.zip
No Hyper-v VM artifacts are present in the .box file. It only contains the vagrantfile and the metadata.json. Also the input
artifacts are being copied to 'c:\users\' folder which was not expected behaviour.
Overview of the Issue
When this post processor is used with artifacts from the 'artifice' post processor along with the provider_override="hyperv", the resulting .box output file does not seem to be valid.
Reproduction Steps
Prerequisite:
Execute : packer build
Observed behaviour:
An incomplete .box file file is generated (see attached file:packer_example_hyperv_amd64.box in the zip file ). packer_example_hyperv_amd64.zip
No Hyper-v VM artifacts are present in the .box file. It only contains the vagrantfile and the metadata.json. Also the input artifacts are being copied to 'c:\users\' folder which was not expected behaviour.
Plugin and Packer version
Simplified Packer Buildfile
file: vagrant_post_processor_hyperv.pkr.hcl
Operating system and Environment details
Log Fragments and crash.log files
See attached log file from the CMD prompt ( packer_build_logt.txt) for the packer build:
packer_build_logt.txt