prepare 5.3.0 release #2266
Open
prepare 5.3.0 release #2266
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 5m 35s |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Here is a little change to address an error while performing the
sendkeysmodule and including a leading slash in thefolderoption. It results as the module not being able to fetch the machine name, hence stopping the playbook and throwing an error instead.ISSUE TYPE
COMPONENT NAME
vmware_guest_sendkey
ADDITIONAL INFORMATION
To reproduce the issue, try executing the vmware_guest_sendkey module and including a folder with a leading slash. It throws an error.
Remove the leading slash to fix it.