Add ability to deploy OVF/VM template from Content Library in vsphere-clone

[ghost]

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

Currently Packer's vsphere-clone builder allows the creation of a new VM from a template using the template: keyword in the JSON configuration. However, should one define a template using a Content Library path Packer cannot find the template. This feature request is to add the ability to define a template from a Content Library for Packer to deploy.

Use Case(s)

Use case would be any time someone is wanting to deploy a VM to a clustered environment. Having a shared Content Library is useful for those configurations and Packer already supports the ability to use Content Libraries for ISOs in vsphere-iso. This would be similar functionality, just using VM templates in vsphere-clone.

Potential configuration

It seems govc already supports doing this using the library.deploy command and giving a path. We may need a new keyword to differentiate between a Content Library path and the VM template functionality already present.

Potential References

https://github.com/vmware/govmomi/blob/master/govc/USAGE.md
https://discuss.hashicorp.com/t/is-it-possible-to-use-an-ovf-template-from-vspheres-content-library-for-vsphere-clone/24117

[ghost]

This issue has been automatically migrated to hashicorp/packer-plugin-vsphere#61 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-vsphere#61.

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.