Skip to content

Zone and node name handling is confusing #1

@jasondegraw

Description

@jasondegraw

Multizone nodes are currently identified with a key (that gets generated?) and by the zone name. The auditor dictionary that contains these nodes uses the key, so it isn't possible to look up connections directly (particularly when distribution links are involved). This needs to be straightened out both here and in the epJSON.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions