hello the idea is packer uses a json file and you can add remove components.
you can have a provisioning script, where packer will run the same script to a qemu and esx, and then the 2 created VMs were provision for the same script. The identical part is not to be taken as one VM will be built and then copied to the other builders. here a virtualbox and vmware example. https://github.com/kikitux/packer_xenial64/blob/master/vagrant/xenial64.json not what you are after, but should help to get an idea. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0exf4yFdtGNQ2%3DQTGo%3DoszcfyZNMkgaD0Uo91t%3DWb1Vx2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
