Mario Lenz
Mario Lenz
@Nina2244 Great! Then we'll track your changes in #1475. I'll try to define one or two integration tests and merge when I have them.
@liamwh @remkolodder If you're still around and interested in this, you might want to have a look at #1536: ``` mkdir -p ~/.ansible/collections/ansible_collections/community git clone https://github.com/ansible-collections/community.vmware ~/.ansible/collections/ansible_collections/community/vmware cd ~/.ansible/collections/ansible_collections/community/vmware git...
@usta Feel free to rebase and merge, I won't object.
@usta FYI: - ansible-community/ansible-build-data#167 - ansible/ansible#79190
I don't think that a simple `destination_network: "{{ network_name }}"` is enough. After all, a VM might have more than one vNIC and therefor possibly require more than one destination...
It would be really great to have a proper API for this instead of having to hack something together using the MOB. But it looks like there isn't any. @Tomorrow9...
I don't think we should implement this in `vmware_guest`, the module is already **far** too complicated. Maybe a new module `vmware_tools_config`? We could start with implementing `syncTimeWithHost` and `syncTimeWithHostAllowed`, but...
@bofillj @MallocArray FYI, @jnm27 and me are working on this: #1553 It's still work in progress, but it would be great if you could test this and tell us if...
recheck
@Nina2244 Looks like you have to rebase. Sorry :-(