-
Notifications
You must be signed in to change notification settings - Fork 347
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
vmware_guest_tools_info: Use toolsVersionStatus2 #2034
Conversation
Build failed. ✔️ ansible-tox-linters SUCCESS in 12m 33s |
recheck |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 10m 41s |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 11m 41s |
@ihumster What do you think about his? |
@ihumster What do you think about this. Should we merge? BTW if you approve, please also try to add the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGFM
Thanks for reviewing @ihumster! |
Build succeeded (gate pipeline). ✔️ ansible-tox-linters SUCCESS in 10m 29s |
Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry. |
Fixes #2033
SUMMARY
toolsVersionStatus
is deprecated andtoolsVersionStatus2
should be used.ISSUE TYPE
COMPONENT NAME
vmware_guest_tools_info
ADDITIONAL INFORMATION
I've just seen that
toolsStatus
is also deprecated. But removing it would be a breaking change...I'll mark this PR WIP until I know what to do about it.Let's deprecate
vm_tools_install_status
in favour ofvm_tools_running_status
/vm_tools_version_status
as an alternative.