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

Add connected_enpoints property to graphql api #11817

Closed
basti1508 opened this issue Feb 24, 2023 · 3 comments · Fixed by #11820
Closed

Add connected_enpoints property to graphql api #11817

basti1508 opened this issue Feb 24, 2023 · 3 comments · Fixed by #11820
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@basti1508
Copy link

basti1508 commented Feb 24, 2023

NetBox version

v.3.4.5

Feature type

Change to existing functionality

Proposed functionality

The netbox graphql api should expose the same connected_endpoints property as the rest api.
This makes it easier to resolve complete paths via graphql.

A query would look like:

  device(id:xx) {
    id
    name
    interfaces {
      name
      connected_endpoints {
        ... on InterfaceType {
          ip_addresses {
            address
          }
          device {
            name
            device_role {
              slug
            }
          }
        }
      }
    }
  }
}

Use case

This function helps on making graphql information analog to rest-Api information.

Database changes

No response

External dependencies

No response

@basti1508 basti1508 added the type: feature Introduction of new functionality to the application label Feb 24, 2023
@basti1508
Copy link
Author

@maintainers: The pull request for this would be ready to be submitted, as soon as this issue is assigned to me.

@basti1508
Copy link
Author

basti1508 commented Feb 24, 2023

ah sorry. Draft PR is more than just a draft..
I'll create a new one then if assigned.

@ryanmerolle
Copy link
Contributor

Relates to #7125

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
3 participants