-
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
Error when installing #7
Comments
Same issue here, @scottcarter87 have you figured this out? |
Same issue. Any luck? @scottcarter87 @RBeaudoin |
I did not have any luck getting this to work. It can be tracked back to a change to packer itself which broke this post-processor. I also tried another ovftool post processor which is maintained by an engineer that works at VMware and that has the exact same problem. Since I was invoking packer from ant I worked around this issue by creating another ant target to take the ovf output that packer spits out already when using the vmware-vmx provider and used tar to bundle it all into a ova. Not ideal but it works. |
I wonder why no one has opened a bug against packer, since it is happening across multiple plugins. Seems like upstream should not break existing plugins... |
Looks like its due to a change to a new packer API? Code here needs modifying to work with the changes to the packer code. Packer is pre-v1 release, so you should expect changes that may break compatibility between releases. |
Looks like this supports v0.8 packer API https://github.com/amitinfo2k/packer-post-processor-ovftool? Thought not sure its fully developed yet? @amitinfo2k |
@gawbul It's complete need to update the installation instructions will be updating asap. for now if you know the packer plugin development u can copy the files manually and build it. |
I am having trouble getting this installed on a ubuntu 14.04 system. I keep getting the following error.
opt/go/src/github.com/iancmcc/packer-post-processor-ovftool/ovftool/post-processor.go:21: undefined: packer.ConfigTemplate
I have tried Packer versions 0.5.1, 0.6.1, and 0.7.5 and I keep getting the same error. I have also tried golang 1.2.1, 1.3, and 1.4 and also get the same error. Not sure how to work around this.
The text was updated successfully, but these errors were encountered: