Add error directive to arista_eos show inventory#2323
Conversation
These states already had patterns that matched all lines, so no new patterns needed to be added to them.
Add error directive and patterns to Transceiver state to make parsing pass successfully.
|
Tested this against real Issues found1. but empty slots print only two: so they fall through to 2. The 3. 4. (non-fatal) Split Model/Description tables Minimal repro
(Remove the Suggested direction
Happy to share the full set of anonymized captures across the platform/version matrix if useful for building out the test fixtures. |
Exactly why I asked if you'd test. 😀
We'll want to match this
Yep, we'll want to add patterns for the storage.
Yep, we'll want to add patterns for the subcomponent section.
Rather than have the PID or DESCR broken on newer SKUs we can fix it in this PR. Good.
If there's raw output from one device that covers all these cases that would be suitable. Otherwise please provide the anonymized raw data for the unique ones that represent the four findings. @surudhi If you'd like to create a PR against my branch and submit me a PR (against my fork), I can include your updates into this branch/PR. Let me know if you're interested in this collaboration. Thank you! |
@mjbear hi, I just opened mjbear#4 against your fork adding my changes to this template along with raw data + yaml files for the issues I encountered. |
During review of PR #2322, it was identified the arista_eos_show_inventory did not have Error directives in its States.
This PR adds those Error directives and any patterns required for parsing to pass successfully against current test data.
I've asked @surudhi if she'd test the modified template against more Arista EOS output.