Change Config Context queryset rendering #8139

Closed
opened 2025-12-29 20:32:57 +01:00 by adam · 2 comments
Owner

Originally created by @arthanson on GitHub (May 30, 2023).

NetBox version

v3.5

Feature type

Change to existing functionality

Proposed functionality

Change Config Context querying to be simpler, or cached in order to simplify the queryset code. This is also a potential blocker to changing the tree code to use django-tree-queries. The current queryset is: https://github.com/netbox-community/netbox/blob/develop/netbox/extras/querysets.py#L67

Use case

The current queries to generate config contexts are quite involved and can be slow. This already caused it to be skipped inclusion in some REST API calls due to the complexity of generating it. Reworking it to be cached or allowing simpler / faster query generation would allow it to be returned in more cases.

Database changes

Depends on implementation.

External dependencies

None.

Originally created by @arthanson on GitHub (May 30, 2023). ### NetBox version v3.5 ### Feature type Change to existing functionality ### Proposed functionality Change Config Context querying to be simpler, or cached in order to simplify the queryset code. This is also a potential blocker to changing the tree code to use django-tree-queries. The current queryset is: https://github.com/netbox-community/netbox/blob/develop/netbox/extras/querysets.py#L67 ### Use case The current queries to generate config contexts are quite involved and can be slow. This already caused it to be skipped inclusion in some REST API calls due to the complexity of generating it. Reworking it to be cached or allowing simpler / faster query generation would allow it to be returned in more cases. ### Database changes Depends on implementation. ### External dependencies None.
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:32:57 +01:00
adam closed this issue 2025-12-29 20:32:57 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Sep 27, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 27, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Oct 28, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 28, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8139