Hello,
This seems like an interesting idea to me!
I've an extra use case to add to Max's one:
We intend to use Packer to create our windows 10 ghost image and deploy it via PXE.
To do so, we start from an iso and a VmWareIso builder, we apply the windows updates (+one or two tweaks) in this first build.
Then we start a new packer build with a VmWareOvf builder that takes the artifact generated above. During this build we run the meat of our provisionning (installing softs via salt-masterless).
And for the last build we also use the generated artifact but this time we are changing the VM's settings to boot via PXE so we can capture the VM.
Since the two first step can take a while (up to 8h cumulated) if I can split those steps and have a "valid" artifact generated at each I can use those to make tests/changes on the next "layer" without having to rerun the whole process.
We where wondering if packer could take another "packer-template" as a builder input and run successive builds by itself? (maybe this already exitst and we did not saw it?)
Or maybe we are taking the wrong direction here?
Best regards,
Loup