I was tasked with starting a discussion regarding adding snapshot capability to vsphere_guest, or perhaps splitting it into a separate module.
I started this work here: https://github.com/ansible/ansible/pull/7690
Dann
I was tasked with starting a discussion regarding adding snapshot capability to vsphere_guest, or perhaps splitting it into a separate module.
I started this work here: https://github.com/ansible/ansible/pull/7690
Dann
Excellent - there’s been some noise about people developing other modules using different vsphere bindings and such, so it’s INFINITELY better that we’re expanding the one in core, as this makes it much nicer to resolve and mix in.
Yep, so given it’s started, what needs to be done to finish?
I think for conversation purposes seeing some examples of the proposed task invocation is a good thing to explore, as I want to see if we may want to keep snapshots as a seperate module (using the same bindings), so the noun is “vmware_snapshot” and maybe it takes a state of “snapped” and “restored” or something?
The other thing that’s currently being discussed is adding support for booting off a cloned image, which probably belongs in the _guest module directly.
Thanks!