You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we can't find a circuit CID based on the full string provided by the parser, perhaps we should have fallback logic to try for substring matches rather than giving up immediately?
Use Case
Example: a Telia notification is parsed to report a circuit ID of the form EON 1234567/2 FRO2006765432 10Gbps CFS 500067890 but in Nautobot the circuit's CID is simply FRO2006765432. Currently we report this as a nonexistent circuit ID - it would be nice if the plugin were "smart" enough to identify this match based on the substring.
The text was updated successfully, but these errors were encountered:
Environment
Proposed Functionality
If we can't find a circuit CID based on the full string provided by the parser, perhaps we should have fallback logic to try for substring matches rather than giving up immediately?
Use Case
Example: a Telia notification is parsed to report a circuit ID of the form
EON 1234567/2 FRO2006765432 10Gbps CFS 500067890
but in Nautobot the circuit's CID is simplyFRO2006765432
. Currently we report this as a nonexistent circuit ID - it would be nice if the plugin were "smart" enough to identify this match based on the substring.The text was updated successfully, but these errors were encountered: