diff options
| author | Rodny Molina <rmolina@linkedin.com> | 2018-05-10 22:15:48 -0700 |
|---|---|---|
| committer | Rodny Molina <rmolina@linkedin.com> | 2018-05-12 18:59:11 -0700 |
| commit | a4364a44ae3180536b8f6faac0ca2f1404915385 (patch) | |
| tree | 94e751b708929ed85394e0ffffe38eda7dface30 /vtysh/vtysh.h | |
| parent | 05859298a3979eaa1a802174128b3342be47c7b1 (diff) | |
vtysh: Extending vtysh to allow question-mark cmds
Currently, "vtysh -c" interface does not provide a logic to parse
commands ending with '?' character. In consequence, the following behavior
is observed:
$ vtysh -c "show bgp ?"
% Unknown command.
With these changes, i'm extending FRR's parser to be able to handle
these commands, which allow a more friendly interaction with users
that rely on "vtysh -c" interface. The typical use-case here is for
scenarios in which the final users relie on external/their-own CLI and
require a friendly interface to FRR's vtysh cli.
$ vtysh -c "show bgp ?"
<cr>
A.B.C.D Network in the BGP routing table to
display
A.B.C.D/M IPv4 prefix
X:X::X:X Network in the BGP routing table to display
X:X::X:X/M IPv6 prefix
attribute-info List all bgp attribute information
cidr-only Display only routes with non-natural netmasks
community Display routes matching the communities
community-info List all bgp community information
...
Signed-off-by: Rodny Molina <rmolina@linkedin.com>
Diffstat (limited to 'vtysh/vtysh.h')
| -rw-r--r-- | vtysh/vtysh.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/vtysh/vtysh.h b/vtysh/vtysh.h index f3e58f309e..ccfdd6557b 100644 --- a/vtysh/vtysh.h +++ b/vtysh/vtysh.h @@ -71,6 +71,7 @@ void vtysh_user_init(void); int vtysh_execute(const char *); int vtysh_execute_no_pager(const char *); +int vtysh_execute_command_questionmark(char *input); char *vtysh_prompt(void); |
