-
Notifications
You must be signed in to change notification settings - Fork 315
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 for VM image exporting #217
Comments
Thanks for submitting this enhancement request. I'll take this item into consideration for some of the near-term updates. Ryan Johnson |
The OVF export option is pretty simple to implement from one of the common variables and the use of local variables. I've implemented this option locally and will include this in the next release. Ryan Johnson |
Adds a common option to export machine image artifacts (`.ovf`,`.vmdk`, and `.mf`) to an output path. #217 Signed-off-by: Ryan Johnson <[email protected]>
Adds a common option to export machine image artifacts (`.ovf`,`.vmdk`, and `.mf`) to an output path. Resolves #217 Signed-off-by: Ryan Johnson <[email protected]>
Hi, Stephen. I've pushed the option to the You'll find the settings in the Ryan Johnson |
Awesome, that's about what I figured it looked like. I was trying to see if I could figure it out myself, and wasn't too far off. Interesting the way packer has you do a for_each, even with a binary value like that. Thank you, this along with the other ansible_user fix are enough that they let me move to your code base instead of customization's I quickly tossed in. |
Thanks for the both the bug report and enhancement request - glad to see the updates being a help to you. If you've not yet done so, consider starring ⭐️ the project in GitHub. It really helps. Ryan Johnson |
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. |
…ples#226) Adds a common option to export machine image artifacts (`.ovf`,`.vmdk`, and `.mf`) to an output path. Resolves vmware-samples#217 Signed-off-by: Ryan Johnson <[email protected]>
Code of Conduct
Description
It would be nice to have a configuration option for downloading the image after it is created.
Use Case(s)
In my use case for this, I am attempting to do the following, which is creating a completely managed content library.
(All of our code is stored inside of Azure Devops)
Potential Configuration
In my version of the code, I am doing the following, but there may be better ways to handle it. I suspect there would be a desire to have a boolean for export or not that falls under the common variables? I am unsure of how to handle that in a packer configuration exactly.
The text was updated successfully, but these errors were encountered: