-
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
Implement encryption configuration for vm vmotion and ft #1779
Implement encryption configuration for vm vmotion and ft #1779
Conversation
Build failed. ❌ ansible-tox-linters FAILURE in 8m 54s |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 8m 47s |
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.
@Alestor Please add a changelog fragment similar to this one. Maybe something like:
minor_changes:
- vmware_guest - add support for configuring vMotion and FT encryption (https://github.com/ansible-collections/community.vmware/issues/1069)
@Alestor Never mind, I already did. That is, if it's OK for you. Feel free to change it if you don't like my text 😃 BTW: I've just realized you've used your main branch for this PR. I really think you should consider feature branches for this in the future. It doesn't really make a difference for us, but it should make live a bit easier for you. |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 33s |
recheck |
Text is fine, thanks for your support on this PR. |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 44s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 34s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 32s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 32s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 34s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 28s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 28s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 47s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 30s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 47s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 48s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 52s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 47s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 34s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 49s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 35s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 43s |
recheck |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 8m 46s |
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.
Thanks @Alestor, I think this is really a valuable new feature. And thanks for having so much patience with our CI 😩
@alinabuzachis @jillr FYI This time the CI succeeded 🎉
Build succeeded (gate pipeline). ✔️ ansible-tox-linters SUCCESS in 8m 27s |
SUMMARY
Fixes #1069
Implements the ability to configured vm encryption settings for vmotion or fault tolerance
ISSUE TYPE
COMPONENT NAME
vmware_guest
ADDITIONAL INFORMATION
Fulfill requirements of #1069