-
Notifications
You must be signed in to change notification settings - Fork 49
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
Workaround prompt issues between ROS 6.49 and 7.1.5 (#62) #161
Conversation
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 for your contribution! Could you please add a changelog fragment? Thanks.
Co-authored-by: Felix Fontein <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #161 +/- ##
==========================================
- Coverage 86.45% 84.57% -1.88%
==========================================
Files 30 32 +2
Lines 3727 3850 +123
Branches 679 710 +31
==========================================
+ Hits 3222 3256 +34
- Misses 367 456 +89
Partials 138 138
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
The sanity check error is because of this:
Co-authored-by: Felix Fontein <[email protected]>
Co-authored-by: Felix Fontein <[email protected]>
@sgrimee thanks a lot for implementing this! |
SUMMARY
This addresses a bug introduced in ROS version 6.69 and resolved in 7.2 that would cause the stdout of commands to contain extraneous characters (often '/' or ':') by adding a whitespace in front of the command.
Fixes #62
ISSUE TYPE
COMPONENT NAME
plugins/module_utils/routeros.py
ADDITIONAL INFORMATION
This is achieved by leveraging the version number that is already collected in
plugins/cliconf
get_capabilities
If for some reason the version was not collected, this change will do nothing to preserve compatibility, but I could not find a case where it is not collected.
Version comparison is made using
from ansible.module_utils.compat.version import LooseVersion
so no new external dependency is added.This fix can be tested with: