-
Notifications
You must be signed in to change notification settings - Fork 339
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
Update 5.0.0 dependencies #2163
Update 5.0.0 dependencies #2163
Conversation
e0e5ff3
to
a151fa0
Compare
Build failed. ✔️ ansible-tox-linters SUCCESS in 7m 46s |
recheck |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 7m 52s |
It looks like we can get rid of some dependencies that were not available on PyPI until recently. @ihumster What do you think? The CI seems to be happy. BTW if you want to implement any other breaking changes, please let me know. I'm working on the next major release ATM. |
a151fa0
to
edf9b8d
Compare
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 7m 49s |
Build succeeded (gate pipeline). ✔️ ansible-tox-linters SUCCESS in 7m 44s |
ac0dd76
into
ansible-collections:main
Fixes #2123
SUMMARY
Require pyVmomi >= 8.0.3.0.1 in order to be able to drop the requirement on the vSAN Management SDK for Python, which has been a pain to install.
Also, substitute the requirement for / dependency on
https://github.com/vmware/vsphere-automation-sdk-python.git
with the PyPI packagesvmware-vcenter
andvmware-vapi-common-client
.Additionally, at least one of those pulls in
requirements
so we can remove it, too.Also document the dependency on ansible-core 2.17.0.
ISSUE TYPE
COMPONENT NAME
requirements.txt
README.md
ADDITIONAL INFORMATION
vSAN Management SDK for Python
vsphere-automation-sdk-python PyPI package
#2153