-
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
Option to skip the image creation #8668
Comments
A solution to this that I've implemented is to wrap the run of
In the case of an amazon-ebs builder, the output is used to delete the AMI and associated snapshot with aws-cli. I'd love to see this as a feature but it would need to be implemented by the provider as probably only the provider would know how to clean things up. |
For more context on similar issues opened for other builders, see #7209 |
@krishicks thanks a lot for your suggestion. I will give it a try and see if that helps :) |
@SwampDragons thanks a lot for pointing me to this thread. |
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. |
Hello Folks,
Can some one please let me know if there is an option in packer to skip/avoid the image creation?
I have a CI/CD pipeline where I am creating image using packer which works pretty great.
However i have another requirement where I have to leverage the same pipeline and offload some steps from Concourse worker by moving some heavy lifting to GCP VM where I can use packer to provision a VM and do the heavy lifting but I don't want to get an output of that packer build. Is there a way I can skip image creation and still do the task?
I will really appreciate some feedback/guidance on this thread.
thanks
The text was updated successfully, but these errors were encountered: