CORRECTION : The attribute is not present in the VMX data file after export, the original post seemed to suggest otherwise ... thanks.
=================================================== Thanks Alvaro. I was originally using the vmx_data attribute value in the Packer JSON file, and using that it does appear when the template is being built, but then not after it's exported to remote vCenter locations. I added the same attribute into vmx_post_data and that had the same effect where the custom attribute is still NOT present in the VMX file on the target vCenter after the export completed. Any other suggestions? The debug log shows this in a few different places ... "Pausing after run of step 'StepCleanVMX'. Press enter to continue." Do I need to reorder my steps in such a way that the clean happens after the attribute is written to the VMX file? Or add a command into the post-provisioner to address this? Thanks, John On Friday, June 2, 2017 at 1:52:36 PM UTC-7, John C wrote: > > I'm using Packer to build a Windows 21012 R2 server image for our VMware > ESXi environment, with all of the code stored in a local GitHub > repository. During the Packer image build process, I get the short > SHA associated with the GitHub commit and then add that to the VMX file as > a custom attribute, so we can associate that image back to the GitHub > commit later. While the image is building, the custom attribute is > definitely in the VMX file, but once it's fully built and OVFTOOL takes > over to clone it to other ESXi locations, this custom attribute is not > present in the cloned image. Is there a way to persist this custom VMX > data throughout the entire Packer image build process, start to finish? > Thanks. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/ae2865f2-c7ee-402a-8b71-1df84104f781%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
