-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add Properties to image #64
Comments
Hi @JoeyG1973 thanks for reaching out here. This is a community maintained plugin so the Packer team won't work on this change. But we are happy to review a pull-request if you are or a member of the community is interested in making the change. That said, are these properties different from the properties that can be set via the the |
Hi @nywilken, The description on external_source_image_properties clarifies nothing so I am not really sure what it is supposed to do. :) |
I am still trying to figure out what https://www.packer.io/plugins/builders/openstack#external_source_image_properties is supposed to be. Is it a filter on properties for what external image to choose or does it set properties on the packer output image? |
Hello, I asked myself the same question a few days ago and found your issue. So here my 2 cents:
Hoping that my comment will be useful. |
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
Please allow the ability to add properties to the image
Use Case(s)
openstack image set --property key=value
needs to be run after the image is created using an external process.Setting properties in OpenStack for the image should be part of packer proper
Potential configuration
Potential References
The text was updated successfully, but these errors were encountered: