--on-error=ask retry should only run the provisioner that errored when using -debug

hashicorp / packer

Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.

http://www.packer.io

Other

15.12k stars 3.33k forks source link

--on-error=ask retry should only run the provisioner that errored when using -debug #13128

Closed MrMMorris closed 3 months ago

MrMMorris commented 3 months ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

--on-error=ask retry should only run the provisioner that errored when also specifying -debug. Currently it reruns all the provisioners in that build unless -debug isn't specified, then it only runs the one that failed.

Let me know if this is intended behavior and I will close.

lbajolet-hashicorp commented 3 months ago

Hi @MrMMorris,

I'm not sure I understand the reruns all the provisioners when combining both arguments; --debug will stop before executing every provisioner/step, letting you debug the state of a system in between two steps, while --on-error lets you decide which action to undertake in case of an error during the build, and rerun is not one of the supported actions AFAIK. Would you be able to provide a template/log example to understand what issue you're running into?

Thanks!

MrMMorris commented 3 months ago

sorry I can't seem to reproduce this right now and I don't think it's a hige issue either way so I will close

github-actions[bot] commented 2 months ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.