David Dreggors

For clarity... ``` - name: Create bootstrap VM from the template vmware_guest: hostname: "{{ vcenter.ip }}" username: "{{ vcenter.admin_username }}" password: "{{ vcenter.admin_password }}" datacenter: "{{ vcenter.datacenter }}" validate_certs: no...

Everything under customvalues is ignored without any error, not one of these keys or values is added

VCSA version is 6.7u3 and customer also tested on another cluster with VCSA at 7.0 On Mon, Sep 26, 2022 at 8:20 AM sky-joker ***@***.***> wrote: > Thanks, @ddreggors ,...

Yes, and we are trying to add these to the virtual machine (`Right click on VM -> Edit Settings -> VM Options -> Advanced -> Configuration Parameters`) so `advanced_settings` are...

ok, I tested with both `vmware_guest`->`advanced_settings` and `vmware_guest_custom_attributes` and the custom attributes is not what I am looking for either but the `advanced_settings` does place these keys and values properly...

So the question is... is advanced_settings meant to replace customvalues or is customvalues still meant to be working? If advanced_settings is the path forward and customvalues is to be replaced...

That is odd, because it does seem to work to replace it. We used to deploy coreos from the ova template using the `customvalues` to set attributes that coreos uses...

we only started testing (and using) advanced_settings after customvalues stopped working. So I would say it only requires it due to the issue with customvalues? Our playbooks always used customvalues...

This PR is now 2 years old (as is the last comment to add `ntp.maxdistance`). We should be aware that we have now added support for multiple distinct cluster vars...

I mis-read the request, yes we should check for the key to exist and only set it it does... no matter where it is set. This can be added via...