Skip to content
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

feat(vmware_guest_snapshot): make module compatible with ESXi hosts w… #2300

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hoppla20
Copy link

@hoppla20 hoppla20 commented Feb 4, 2025

SUMMARY

Due to the current restriction that the datacenter paramter is required, the vmware_guest_snapshot module is not compatible with ESXi hosts without vCenter, even though ESXi with license also exposes this API. This PR removes the restriction of requiring the datacenter parameter and removes the vCenter part from the module description.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

vmware_guest_snapshot

ADDITIONAL INFORMATION

This change was tested against an ESXi 7.0 Update 3 host (with license) without a vCenter.

@hoppla20
Copy link
Author

hoppla20 commented Feb 4, 2025

I will check on the tests later, I havn't checked the implications of this change when using it against a vCenter

@hoppla20 hoppla20 changed the title feat(vmware_guest_snapshot): make module compatible with ESXi hosts w… Draft: feat(vmware_guest_snapshot): make module compatible with ESXi hosts w… Feb 4, 2025
@hoppla20 hoppla20 marked this pull request as draft February 19, 2025 11:01
@hoppla20 hoppla20 changed the title Draft: feat(vmware_guest_snapshot): make module compatible with ESXi hosts w… feat(vmware_guest_snapshot): make module compatible with ESXi hosts w… Feb 19, 2025
@hoppla20
Copy link
Author

So I have tested the change on a vCenter 7 and it should be working. This PR also doesn't change how this module functions. It only makes the datacenter argument optional and updates the module description.

I have also checked the failing test and I don't see any reason why this PR should have any effect on the test. I there a way for me to restart the test, in order to check whether it was just flaky?

@hoppla20 hoppla20 marked this pull request as ready for review February 19, 2025 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant