animatco

I would agree, that it would make life easier for those wanting to always have the latest version of the code with-out regression testing. One point though from a security...

This actually looks handy

gather_facts for 2019, 2022, 2025 for vSphere nodes LWTST2025 | SUCCESS => { "ansible_facts": { "ansible_architecture": "64-bit", "ansible_architecture2": "x86_64", "ansible_bios_date": "06/25/2021", "ansible_bios_version": "VMW71.00V.18227214.B64.2106252220", "ansible_date_time": { "date": "2024-12-26", "day": "26", "epoch":...

So we tested again on both a 2019 and 2022 Windows Server on vSphere. They failed at the 1.2.1 section, when we manually modified the prelim. - name: Set Fact...

additional information from gather facts: Azure: "ansible_system_vendor": "Microsoft Corporation", "ansible_virtualization_role": "guest", "ansible_virtualization_tech_guest": [ "VirtualPC" ], "ansible_virtualization_tech_host": [ "kvm" ], "ansible_virtualization_type": "VirtualPC", Google: "ansible_system_vendor": "Google", "ansible_virtualization_role": "guest", "ansible_virtualization_tech_guest": [ "kvm" ],...

Just to let you know the latest update resolved the issue.