Skip to content

vmware: name vcf-sdk as the tag sync dependency - #572

Open
semx wants to merge 1 commit into
developmentfrom
fix/vcf-sdk-naming
Open

semx wants to merge 1 commit into
developmentfrom
fix/vcf-sdk-naming

Conversation

@semx

@semx semx commented Sep 30, 2026

Copy link
Copy Markdown
Collaborator

Closes #569.

The tag sync option group (settings-example.ini, module/sources/vmware/config.py) and the import failure warning in module/sources/vmware/connection.py still named vsphere-automation-sdk. That package is archived and its runtime imports pkg_resources unconditionally, which does not exist on Python 3.12+ with setuptools >= 82 (requirements.txt pins 84.0.0 now), so anyone following the old name ends up with "Tag syncing will be disabled".

The README and the Dockerfile already install vcf-sdk. Its runtime (vmware-vapi-runtime 9.1.1.0) imports without pkg_resources: with the current pins, python -W error::UserWarning -c "from vmware.vapi.vsphere.client import create_vsphere_client; from com.vmware.cis.tagging_client import Tag" passes while import pkg_resources fails; same in the published development image. This names vcf-sdk in the option description and in the warning, with the install command. Full suite with vcsim: 257 passed.

The tag sync option group and the import failure warning still named
vsphere-automation-sdk. That package is archived and its runtime imports
pkg_resources unconditionally, which no longer exists on Python 3.12+ with
setuptools >= 82, so following the old name ends with "Tag syncing will be
disabled" (#569). The README and the Dockerfile already use vcf-sdk, whose
runtime (9.1.1.0) imports without pkg_resources. Name it in the option
description and in the warning, and tell the user what to install.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant