Skip to content

added support for multiple IPs on juniper interface #347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 3, 2025

Conversation

susanhooks
Copy link
Contributor

Closes: #346

What's Changed

Fixes bug where multiple IPs on a juniper interface were not being parsed. New functionality adds support for multiple IPs.

`In [4]: item = [{'prefix_length': ['172.22.0.0/28', '172.22.0.0/28'], 'ip_address': ['172.22.0
...: .1', '127.22.0.2']}]

In [5]: parse_junos_ip_address(item)
Out[5]:
[{'prefix_length': '28', 'ip_address': '172.22.0.1'},
{'prefix_length': '28', 'ip_address': '127.22.0.2'}]
`

To Do

  • Explanation of Change(s)
  • Added change log fragment(s) (for more information see the documentation)
  • Attached Screenshots, Payload Example
  • Unit, Integration Tests
  • Documentation Updates (when adding/changing features)
  • Outline Remaining Work, Constraints from Design

Copy link
Contributor

@Dav-C Dav-C left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@scetron scetron merged commit 897ea3f into develop Apr 3, 2025
15 checks passed
@scetron scetron deleted the fix-junos-interface branch April 3, 2025 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Juniper not parsing multiple IP addresses per interface
3 participants