-
Notifications
You must be signed in to change notification settings - Fork 735
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
Issue #384 cisco_asa_show_route - Fix uptime issue #401
Conversation
…e parsed data for tests
Sorry for the sloppy commits. Please feel free to squash merge if you choose to merge. Let me know if there are any comments/fixes that need to be looked at with this, but the issue was fairly straightforward. The value Thanks, Brandon |
Also fixed, the uptime value only accounted for the |
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.
@brandomando Do you mind uploading a separate .raw and .parsed files for the tests rather than editing the existing one? After that change and tests passing, I will get this merged in.
@@ -6,7 +6,7 @@ Value DISTANCE (\d+) | |||
Value METRIC (\d+) | |||
Value NEXTHOPIP (\d+\.\d+\.\d+\.\d+) | |||
Value NEXTHOPIF (\S+) | |||
Value UPTIME (\d+:\d+:\d+) | |||
Value UPTIME ((\d+:\d+:\d+)|(\d+w\d+d)) |
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.
Does \S+
work for UPTIME? I'm sure this converts to \d+y\d+d
after a year.
ISSUE TYPE
COMPONENT
cisco_asa_show_route
SUMMARY
Uptime populating into nexthopif value because the uptime value was not placed into the template correctly.
Fixes #384
Before:
After: