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

Expose dynamic groups containing devices on the devices themselves in GraphQL #2307

Closed
2 of 12 tasks
Kircheneer opened this issue Aug 25, 2022 · 1 comment · Fixed by #2315
Closed
2 of 12 tasks

Expose dynamic groups containing devices on the devices themselves in GraphQL #2307

Kircheneer opened this issue Aug 25, 2022 · 1 comment · Fixed by #2315
Labels
type: feature Introduction of new or enhanced functionality to the application

Comments

@Kircheneer
Copy link
Contributor

As ...

Austin - Network Automation Engineer

I want ...

a dynamic_groups field to be available in GraphQL for devices like

query ($device_id: ID!) {
  device(id: $device_id) {
    dynamic_groups
  }
}

So that ...

I can query via GraphQL which dynamic groups a given device belongs to.

I know this is done when...

the dynamic_groups field is available on the GraphQL model for devices.

Optional - Feature groups this request pertains to.

  • Automation
  • Circuits
  • DCIM
  • IPAM
  • Misc (including Data Sources)
  • Organization
  • Plugins (and other Extensibility)
  • Security (Secrets, etc)
  • Image Management
  • UI/UX
  • Documentation
  • Other (not directly a platform feature)

Database Changes

None

External Dependencies

None

@Kircheneer Kircheneer added the type: feature Introduction of new or enhanced functionality to the application label Aug 25, 2022
@Kircheneer
Copy link
Contributor Author

I will try and tackle this. Should look something like this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature Introduction of new or enhanced functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant