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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow ability to configure whether built Docker image should be kept #14

Open
h-arlt opened this issue Aug 12, 2020 · 1 comment
Open

Comments

@h-arlt
Copy link
Contributor

h-arlt commented Aug 12, 2020

Once the built Docker image has been successfully pushed to the configured registry, the question arises whether it should be kept in local registry at all.

As this might differ from situation to situation, the user should be able to configure the desired behaviour. Thus, we should introduce a new user variable, say keep_image, that defaults to true and pass its value to Packer's docker-push post-processor.

@h-arlt
Copy link
Contributor Author

h-arlt commented Aug 12, 2020

There is a bug - marked as 'wont-fix' - which prevents us from extracting the keep_input_artifact parameter of docker-push post-processor as user variable (it only accepts bool values but user variables are string -> string mappings).

Only solution would be transform all packer scripts and variable files to the new HCL2 format (still in beta).

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

No branches or pull requests

1 participant