In anticipation of the upcoming release of NetBox v3.6, the first beta release is now available on GitHub! This release introduces a bunch of new features, and lays the foundation for internationalization support (coming in v4.0).
A complete accounting of the changes coming in v3.6 is provided below. A public demo of this release is available for testing at beta-demo.netbox.dev.
device_role
field on the Device model has been renamed to role
. The device_role
field has been temporarily retained on the REST API serializer for devices for backward compatibility, but is read-only.choices
array field has been removed from the CustomField model. Any defined choices are automatically migrated to CustomFieldChoiceSets, accessible via the new choice_set
field on the CustomField model.napalm_driver
and napalm_args
fields (which were deprecated in v3.5) have been removed from the Platform model.Management views for the following object types, previously available only under the backend admin interface, have been relocated to the primary user interface:
This migration provides a more consistent user experience and unlocks advanced functionality not feasible using Django’s built-in views. The admin UI is scheduled for complete removal in NetBox v4.0.
Administrators now have the option of configuring default permissions for all users globally, regardless of explicit permission or group assignments granted in the database. This is accomplished by defining the DEFAULT_PERMISSIONS
configuration parameter. By default, all users are granted permission to manage their own bookmarks and API tokens.
Users can now bookmark their favorite objects in NetBox. Bookmarks are accessible under each user’s personal bookmarks list, and can also be added as a dashboard widget.
Selection and multi-select custom fields now employ discrete, reusable choice sets containing the valid options for each field. A choice set may be shared by multiple custom fields. Additionally, each choice within a set can now specify both a raw value and a human-friendly label (see #13241). Pre-existing custom field choices are migrated to choice sets automatically during the upgrade process.
Users now have the option to employ one of several pre-defined sets of choices when creating a custom field. These include:
When defining a choice set, one of the above can be employed as the base set, with the option to define extra, custom choices as well.
Tags may now be restricted to use with designated object types. Tags that have no specific object types assigned may be used with any object that supports tag assignment.
rf_role
to InterfaceTemplatedevice_role
field on Device to role
for consistency with VirtualMachineChoiceField
and MultipleChoiceField
classesnapalm_driver
and napalm_args
from Platformaccount
app for better organization