-
Notifications
You must be signed in to change notification settings - Fork 338
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
[WIP] Simplified guest module #2052
base: main
Are you sure you want to change the base?
[WIP] Simplified guest module #2052
Conversation
d825455
to
d1f230f
Compare
d1f230f
to
9d48694
Compare
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 10m 53s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 11m 45s |
03fda7c
to
ec85f8c
Compare
Build failed. ✔️ ansible-tox-linters SUCCESS in 10m 10s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 12m 17s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 10m 35s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 11m 52s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 11m 06s |
37e934e
to
62dbb00
Compare
Build failed. ✔️ ansible-tox-linters SUCCESS in 11m 40s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 10m 59s |
SUMMARY
I think the
vmware_guest
module tries to do too many things at once and, in consequence, is far to complex and pretty much unmaintainable. Maybe we should try and create a simpler module that's easier to maintain and move some functionality to other (possibly new) modules.ISSUE TYPE
COMPONENT NAME
guest
vmware_guest
ADDITIONAL INFORMATION
ansible-collections/vmware.vmware#4 (comment)