Conversation
Signed-off-by: Fredi Raspall <fredi@githedgehog.com>
Signed-off-by: Fredi Raspall <fredi@githedgehog.com>
Signed-off-by: Fredi Raspall <fredi@githedgehog.com>
qmonnet
left a comment
There was a problem hiding this comment.
I'm not sure about show tech as a command name, I don't really understand what tech refers to in this context. Something like show state or show context would seem more appropriate to me.
Other than that, I've got two comments below, but mostly everything seems in order, thanks!
Comes from show tech-support. I believe Cisco was the first to use this terminology, but other vendors of networking equipment have similar commands (Arista, Hp...) |
27289d2 to
f010e01
Compare
We handle it by iterating over all handlers, pretending that they were individually invoked, and merging all of the results into one response. Signed-off-by: Fredi Raspall <fredi@githedgehog.com>
Signed-off-by: Fredi Raspall <fredi@githedgehog.com>
Signed-off-by: Fredi Raspall <fredi@githedgehog.com>
- Simplify the impl of Display for FlowKey so that no strings are created for intermediate data. - Move impl Display of FlowInfo together with impl Display for FlowKey and rename file. - Adjust the layout of the flow table to improve readability - Use upper case for protocol acronyms Signed-off-by: Fredi Raspall <fredi@githedgehog.com>
f010e01 to
97596d1
Compare
I didn't know that, thanks for the explanation. Sounds good then! 👍 |
Sample
The flow table now looks as: