Skip to content
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

link peers on a cable termination are not cast to a specific model but are left as a generic record. #519

Open
arthanson opened this issue Dec 8, 2022 · 0 comments
Labels
status: blocked Another issue or external requirement is preventing implementation type: feature Introduction of new functionality to the application

Comments

@arthanson
Copy link
Collaborator

link peers on a cable termination are not cast to a specific model but are left as a generic record. The return for link_peers is somewhat different format then for things like a_terminations:

        "a_terminations": [
            {
                "object_type": "circuits.circuittermination",
                "object_id": 15,
                "object": {

For link_peers the return is:

            "link_peers": [
                {
                    "id": 1,
            "link_peers_type": "circuits.circuittermination",

It would make it easier on the API side if these were consistent (would require a change on the NetBox side):

        "link_peers": [
            {
                "object_type": "circuits.circuittermination",
                "object_id": 1,
                "object": {
@abhi1693 abhi1693 added status: blocked Another issue or external requirement is preventing implementation type: feature Introduction of new functionality to the application labels Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: blocked Another issue or external requirement is preventing implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants