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

GraphQL: rendered config_context not available on device/VM level #6832

Closed
sdktr opened this issue Jul 28, 2021 · 3 comments
Closed

GraphQL: rendered config_context not available on device/VM level #6832

sdktr opened this issue Jul 28, 2021 · 3 comments
Assignees
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@sdktr
Copy link
Contributor

sdktr commented Jul 28, 2021

NetBox version

v3.0-beta1

Python version

3.8

Steps to Reproduce

  1. Open GraphiQL
  2. Fetch a single device (example query)
  3. Try to get the rendered config context for the device

Expected Behavior

The GQL schema presents an attribute that will fetch the rendered config context. No such attribute is found on the generated graphQL schema.

Observed Behavior

No attribute is available. Note: local_config_context is a directly assigned/attached attribute, but this is not the rendered config_context as present in the REST API.

@sdktr sdktr added the type: bug A confirmed report of unexpected behavior in the application label Jul 28, 2021
@ryanmerolle ryanmerolle added the beta Concerns a bug/feature in a beta release label Jul 28, 2021
@sdktr
Copy link
Contributor Author

sdktr commented Jul 28, 2021

possibly related to #6829 (slack comment from @ryanmerolle )

@ryanmerolle
Copy link
Contributor

ryanmerolle commented Jul 28, 2021

Yep, it is not being auto rendered, we just have to see why. Issue #6829 is because those items are GenericForeignKeys. This is not.

@ryanmerolle
Copy link
Contributor

This is what the beta is for.

Thanks for identifying this issue @sdktr. Please keep hitting the graphql feature and help us identify any more issues before a stable release is cut. I will be doing the same.

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jul 29, 2021
@jeremystretch jeremystretch self-assigned this Aug 4, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants