Yeah, this is what I thought, however:
Imagine the following ansible playbook:
---
- hosts: all
tasks:
- include: ansible_playbooks/tester2017-07-25-14-07-45test.yaml
ignore_errors: yes
- include: ansible_playbooks/admin2017-07-31-14-28-38test.yaml
ignore_errors: yes
- include: ansible_playbooks/admin2017-08-01-15-06-39test.yaml
ignore_errors: yes
I am skipping faulty playbooks with this. This works as planned when using
ansible-playbook alone. The Exit Code is 0. (checked with echo $?).
However, packer still aborts on the first error. I have no experience in
golang so I am not able to find our in the source, why this is treated as
an error exit.
Am Freitag, 25. August 2017 15:39:07 UTC+2 schrieb Alex Walender:
>
> Hi there,
>
> is there a way to skip provisioner tasks when they fail? Right now the
> whole build aborts when a provisioner fails.
>
--
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/07da4797-746e-419d-83f9-1dd3980549f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
