Update the requirements to vcf-sdk

[mariolenz]

I suggest to update the requirements to vcf-sdk. As far as I understand, this package includes pyvmomi, vmware-vcenter and vmware-vapi-common-client.

And maybe some additional stuff that might be useful in the future.

Additional information: I'm doing the same thing in community.vmware: ansible-collections/community.vmware#2457

@mikemorency Feel free to close this issue if you don't want to do this, and even the 3.0.0 milestone that I've created if you don't like it!

[mikemorency]

Vcf requires python 3.9 or higher and ansible core 2.18 still supports py3.8 on remote hosts. So I think this collection cant switch until that is EOL?

[mariolenz]

The modules of this collection don't run on remote (vCenter / ESXi) hosts but on the controller and connects to the remote host via API. Or am I wrong? So I don't see a problem there.

Anyway, I'm not suggesting to do this now. I suggest to do this in the next major release, that is 3.0.0. Maybe you're planning to drop ansible-core < 2.19 for 3.0.0, anyway, so we would be doubly sure there.

[mikemorency]

The modules run on either the local (controller) host or a remote host, and then that host connects to vcenter/esxi. localhost is the more common use case IMO, but people can run these modules using a remote host due to security or network restrictions

[mariolenz]

True, that's possible. But I don't know the requirements for remote hosts in this sense. I should think they are the same as for controllers, but I didn't find this documented anywhere.

I think this would be a breaking change. So we would have to wait for a new major release, anyway. But I'm sure that vcf-sdk is something worth considering. And so we don't forget, I've created a milestone for 3.0.0 and added this issue there.

When you start working on 3.0.0, we can review this again. And then we can implement this, decide against vcf-sdk and close the issue as wontfix, or move it to the 4.0.0 milestone. Whatever makes more sense then 😃

[mariolenz]

I'm not sure, but when depending on vcf-sdk in a future major release this might be interesting: Unified Authentication in VMware Cloud Foundation SDK 9.0: Seamless authentication across vSphere and vSAN APIs