Skip to content

pullUpInterface's portUniquify should provide null physical port instead of throw exceptions when non-single port mapping exists #4

@mkorbel1

Description

@mkorbel1

Motivation

Currently, if there are 0 or >1 logical ports mapped to an interface, then the portUniquify function can't be called since it only works with exactly 1 physical port present. This is annoying if there are multiple physical ports or no physical ports mapped to at least one logical port, but you don't need to use the physical name for uniquification.

Desired solution

Rather than throwing an exception, it would be nice to just make the function signature provide null for cases where there isn't exactly one physical port mapping. Then logical uniquification can still be done.

Alternatives considered

No response

Additional details

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions