Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add skip_create_image config parameter to builder #86

Open
Voldemat opened this issue Sep 5, 2023 · 1 comment
Open

Add skip_create_image config parameter to builder #86

Voldemat opened this issue Sep 5, 2023 · 1 comment

Comments

@Voldemat
Copy link

Voldemat commented Sep 5, 2023

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

The feature is fairly simple, if skip_create_image=true we don`t publish AMI in cloud, just run defined provisioners to ensure that all scripts are correct. Otherwise, is skip_create_image=false whole process left unchanged.
I can create pull request for that, just wanna make sure you are cool with it.

Use Case(s)

For example, I have CI/CD pipeline where I build packer image. So I add changes to build configuration in some branch, let`s say feature/change-packer. Now I want to check my scripts are correct before I merge into main branch. In order to do that, whole building process should run but without publishing actual AMI image, it would be done in the main branch.

Potential configuration

skip_create_image=false

Potential References

Such feature already implemented in Google Packer Plugin, link to pull request provided below.
hashicorp/packer#10496

@apricote
Copy link
Member

apricote commented Dec 4, 2023

We are open to merging a pull request for this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants