Huawei smartax display ont info summary

[evilmonkey19]

Fixing bug when having multiple outputs from different ports

[mjbear]

Fixing bug when having multiple outputs from different ports

Howdy @evilmonkey19!
There are some merge conflicts that need fixed up. I'll see about these later today.

I have a few thoughts on some regexes, but it won't be until later that I can monkey with those to see how what I think translates when parsing the test data.

[evilmonkey19]

Howdy @mjbear ! No problem 😄. I know that aren't the best templates ever, but they are quite difficult to do, specially because of the multiple ports output.

[mjbear]

@evilmonkey19
I submitted a PR evilmonkey19#4 against your branch to clean up the merge conflicts.

Other items:
🎯 There's a template for huawei_smartax_display_ont_info_summary_sn.textfsm in this PR as well. Was that intended?

🌎 It does not appear there is test data for the summary_sn template.

Thank you.
Merry Christmas! 🎄

[evilmonkey19]

Howdy @mjbear!

This is not quite an usual template as you may see that there are multiple tables into one. The technique used here is using two templates and do the matching using the key keyword. Instead of seeing both as 2 separate templates you should see them as only one. Actually, the resulting YAML file have variables from both templates. For instance, just looking at one template and the resulting YAML you will more variables in the YAML file than in the template.

This is a special technique that @jvanderaa and @jmcgill298 told me long ago :)

[mjbear]

Howdy @mjbear!

This is not quite an usual template as you may see that there are multiple tables into one. The technique used here is using two templates and do the matching using the key keyword. Instead of seeing both as 2 separate templates you should see them as only one. Actually, the resulting YAML file have variables from both templates. For instance, just looking at one template and the resulting YAML you will more variables in the YAML file than in the template.

Ah, that makes sense.

This is a special technique that @jvanderaa and @jmcgill298 told me long ago :)

Neat, I'll have to give this more of a look shortly.