Searching for virtual machines or devices omits config context in results (api) #2653

Closed
opened 2025-12-29 18:20:54 +01:00 by adam · 1 comment
Owner

Originally created by @ossark on GitHub (Jun 5, 2019).

Environment

  • NetBox version: 2.5.8

Steps to Reproduce

  1. fetch a virtual machine or device via api (https://netbox/api/virtualization/virtual_machines/?name=your-machine-name)
  2. config_context is not present in the results

Expected Behavior

config_context to be present as it is when one uses the direct id reference to the object like so:
https://netbox/api/virtualization/virtual_machines//

Observed Behavior

No config_context was returned in the results

Originally created by @ossark on GitHub (Jun 5, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * NetBox version: 2.5.8 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. fetch a virtual machine or device via api (https://netbox/api/virtualization/virtual_machines/?name=your-machine-name) 2. config_context is not present in the results <!-- What did you expect to happen? --> ### Expected Behavior config_context to be present as it is when one uses the direct id reference to the object like so: https://netbox/api/virtualization/virtual_machines/<id>/ <!-- What happened instead? --> ### Observed Behavior No config_context was returned in the results
adam closed this issue 2025-12-29 18:20:54 +01:00
Author
Owner

@lampwins commented on GitHub (Jun 5, 2019):

This is expected behavior in 2.5, but this will be changing in 2.6 such that config_context will be included by default.

@lampwins commented on GitHub (Jun 5, 2019): This is expected behavior in 2.5, but this will be changing in 2.6 such that `config_context` will be included by default.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2653