We were using a regexp to detect the prompt of IOS after a command output had completed. This was causing to misparse many entries. IOS (and XE) devices have a fixed prompt: [hostname]> or [hostname]#. For example, leaf01> or leaf01#.
This patch fixes the prompt to be an exact match based on these possibilities. Furthermore, in certain cases, when we attempt to enable privilege escalation, we were no handling the case where the enable command itself failed. We now handle that as well.
Proposed Release Note Entry
Use string tuples and an understanding of IOS(XE) prompts to detect the end of command output.
[X] I have read the comments and followed the CONTRIBUTING.md.
[X] I have explained my PR according to the information in the comments or in a linked issue.
[X] My PR source branch is created from the develop branch.
We were using a regexp to detect the prompt of IOS after a command output had completed. This was causing to misparse many entries. IOS (and XE) devices have a fixed prompt: [hostname]> or [hostname]#. For example, leaf01> or leaf01#.
This patch fixes the prompt to be an exact match based on these possibilities. Furthermore, in certain cases, when we attempt to enable privilege escalation, we were no handling the case where the enable command itself failed. We now handle that as well.
Proposed Release Note Entry
Use string tuples and an understanding of IOS(XE) prompts to detect the end of command output.
developbranch.developbranch.--signoffapplied