Open andyshinn opened 1 month ago
Hi @andyshinn,
I'm not sure what you're trying to do exactly, but from Packer's perspective, a build that doesn't create an AMI does not expose artifacts, so besides post-processors like shell-local
, you probably won't be able to run any since there's no artifact to process.
I'm veering towards not classifying this as a bug/enhancement, since it looks fundamentally incompatible with what Packer aims to do, but please feel free to push back on that, there might be a valid use-case that I'm missing here.
Thanks!
Specifically, I am trying to use the artifice
post-processor. According to the first couple sentences of the post-processor it seems perfectly normal to want to do something like this: https://developer.hashicorp.com/packer/docs/post-processors/artifice
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 "me too" comments, 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
Post-processors are not run when
skip_create_ami
istrue
.Use Case(s)
I am trying to run some EC2 instances to build and download an artifact and then add it to the manifest with the
artifice
andmanifest
post-processors. But they don't appear to work when I don't want to keep the AMI withskip_create_ami
.Potential configuration
Potential References