-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dry run option to skip steps past the provisionning #1739
Comments
Solved in #1740 |
Can i use this dry-run option for azure ? i dont see the option in the docs ? Thanks |
This hasn't been implemented. |
Do we know when this will be released ? also is there another way to build the packer image and run all the provisioners and then clean up everything without saving the image ? |
Just add a provisioner that exits with a non 0 status last in your
provisioner block.
…On Nov 15, 2017 18:42, "hesamaseh" ***@***.***> wrote:
Do we know when this will be released ? also is there another way to build
the packer image and run all the provisioners and then clean up everything
without saving the image ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1739 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAiCgxkRZX4NNqc8JvGmI9mBEgCTXsQWks5s2yKCgaJpZM4DGZpB>
.
|
ghost
locked and limited conversation to collaborators
Apr 4, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to have a
--dry-run
option that allows an image to be prepared (for EC2 EBS for example it would mean creating an instance and running the provisioners) without doing the actual creation of the image (again for EC2, the creation of the AMI).This would allow testing the provisioning of new images without the hassle of managing the resulting image. Particularly useful in CI context.
The text was updated successfully, but these errors were encountered: