Chaining vsphere-iso builders, is it possible, or should I use different tools?

I have a working vsphere-iso builder (along with provisioners) that produces a Windows Server 2019 vm, which I then convert to .ova (after adding vApp properties through PowerCLI).

I want to create a second packer template that uses this .ova as a base (similar to how vsphere-clone can use regular vSphere templates as a base), but I have not been able to find any information about how to set up such a chain.

Does anyone have suggestions/more information that could point me in the right direction?

(Iā€™m right now tempted to first deploy a VM through terraform, but really hoping I can avoid this)

Maybe this could help you out:

Thanks for pointing me to that article; I did see it a while ago but forgot about it again :slight_smile:

I ended up using post-processors vsphere and vsphere-template; which re-registers the VM generated by builder vsphere-iso as a vSphere template.
Then for my downstream packer template I use vsphere-clone as builder.

1 Like