-
Notifications
You must be signed in to change notification settings - Fork 448
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
fix: allow datastore_cluster
for content library clones
#2061
fix: allow datastore_cluster
for content library clones
#2061
Conversation
Hi @bFekete could you please provide a HCL which deploys a VM from content library on datastore cluster and has output some of the newly created VM properties , like the id for example? This must be executed with version of the provider containing your fix. The output of Best Regards, Vasil |
datastore_cluster_id
for content library clones
Can't provide all that info due to policies. data "vsphere_datacenter" "this" {
name = "test-dc"
}
data "vsphere_datastore_cluster" "this" {
name = "test-dsc"
datacenter_id = data.vsphere_datacenter.this.id
}
data "vsphere_content_library" "library" {
name = "test-cl"
}
data "vsphere_content_library_item" "ovf" {
name = "test-ovf-template"
type = "ovf"
library = data.vsphere_content_library.library.id
}
resource "vsphere_virtual_machine" "this" {
....
datastore_cluster_id = data.vsphere_datastore_cluster.this,id
clone {
template_uuid = data.vsphere_content_library_item.ovf.id
customize {
...
}
}
...
} |
Here's an example from a project I maintain. Just change to datastore cluster datasource and use it in |
datastore_cluster_id
for content library clonesdatastore_cluster_id
for content library clones
Hi. Is there any work required to merge this? |
Yes, it needs review, testing, and regression testing before merged - when time permits us to prioritize. |
There is contradicting content product documentation and the KB. Documentation: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vm-administration/GUID-6EA309BC-9113-449C-B668-ACBB363485C3.html infers supported. KB: https://kb.vmware.com/s/article/91103 states that it is not supported. I'll track this item down with engineering so that this can be reviewed and any contradictory information resolved. |
ca1ba09
to
65ab6e9
Compare
Hi @tenthirtyam. What's the issue preventing this fix from being merged? |
Please refer to #2061 (comment). |
65ab6e9
to
6e0af62
Compare
6e0af62
to
552a385
Compare
The PR is specific for provisioning a VM by cloning an OVF from a content library. It was tested against content library clones. In your test code, you are using the data source ovf vm template which doesn’t even support ovfs from a content library. Also it looks like its using an OVF deploy instead of a clone |
Thanks for clarifying the use case. I'll review again tomorrow. |
datastore_cluster_id
for content library clonesdatastore_cluster
for content library clones
Allows specifying a `datastore_cluster_id` for `vsphere_virtual_machine` when cloning from `vsphere_content_library_item`. Co-Authored-By: Ryan Johnson <[email protected]>
39c7a45
to
9dda838
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made some slight modifications pushed to 9dda838.
This has been tested in our environments and is good to ship.
LGTM
This functionality has been released in v2.8.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Allows specifying a
datastore_cluster_id
forvsphere_virtual_machine
when cloning fromvsphere_content_library_item
.References
Closes #2055
https://kb.vmware.com/s/article/91103