Search code examples
windowsmultiplatformpacker

What happens to the provisioner "shell-local" from packer when we run it on windows

i am talking about this provisioner: https://www.packer.io/docs/provisioners/shell-local.html.

I am running a packer build that uses a vagrant base box (debian/jessie64) so i need to download vagrant and download that base box. But i need this packer build to run the same in windows.

So how does windows treats the shell-local provisioner can i just do:

        "provisioners": [
          {"type": "shell-local",
              "command": "vagrant box add --name debian-vagrant-development box/modified-debian-VAGRANTSLASH-jessie64"},
          {"type": "shell",
              "inline": ["echo 'my additional provisioning steps'"]}
              ],

Which i am pretty sure i can't, and in that case; which is the alternative?, do i just make this in ansible and put packer to run it.

Solution

  • Too big of a task for what it actually accomplish, is not really practical for my use case. In the case is needed i'll say use ansible or chef or what you use for provision to keep the portability. Thank you.