starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

[PR #9041] [MERGED] Release v3.2.0 #13425

New Issue
Closed
opened 2025-12-29 22:27:20 +01:00 by adam · 0 comments
adam commented 2025-12-29 22:27:20 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/9041
Author: @jeremystretch
Created: 4/5/2022
Status: ✅ Merged
Merged: 4/5/2022
Merged by: @jeremystretch

Base: master ← Head: develop

📝 Commits (10+)

📊 Changes

498 files changed (+20501 additions, -11383 deletions)

View changed files

📝 .github/ISSUE_TEMPLATE/bug_report.yaml (+1 -1)
📝 .github/ISSUE_TEMPLATE/feature_request.yaml (+1 -1)
📝 .github/workflows/ci.yml (+4 -3)
➕ .readthedocs.yaml (+10 -0)
📝 base_requirements.txt (+11 -2)
📝 docs/configuration/dynamic-settings.md (+16 -0)
📝 docs/configuration/index.md (+6 -1)
📝 docs/configuration/optional-settings.md (+92 -0)
📝 docs/core-functionality/device-types.md (+1 -0)
📝 docs/core-functionality/devices.md (+1 -0)
➕ docs/core-functionality/modules.md (+4 -0)
📝 docs/core-functionality/services.md (+1 -0)
📝 docs/customization/reports.md (+1 -1)
📝 docs/development/adding-models.md (+1 -1)
📝 docs/development/getting-started.md (+38 -19)
📝 docs/development/release-checklist.md (+1 -1)
📝 docs/development/user-preferences.md (+8 -5)
📝 docs/index.md (+1 -1)
📝 docs/installation/3-netbox.md (+7 -12)
📝 docs/installation/index.md (+1 -1)

...and 80 more files

📄 Description

Breaking Changes

  • Automatic redirection of legacy slug-based URL paths has been removed. URL-based slugs were changed to use numeric IDs in v2.11.0.
  • The asn field has been removed from the site model. Please replicate any site ASN assignments to the ASN model introduced in NetBox v3.1 prior to upgrading.
  • The asn query filter for sites now matches against the AS number of assigned ASN objects.
  • The contact_name, contact_phone, and contact_email fields have been removed from the site model. Please replicate any data remaining in these fields to the contact model introduced in NetBox v3.1 prior to upgrading.
  • The created field of all change-logged models now conveys a full datetime object, rather than only a date. (Previous date-only values will receive a timestamp of 00:00.) While this change is largely unconcerning, strictly-typed API consumers may need to be updated.
  • A pre_run() method has been added to the base Report class. Although unlikely to affect most installations, you may need to alter any reports which already use this name for a method.
  • Webhook URLs now support Jinja2 templating. Although this is unlikely to introduce any issues, it's possible that an unusual URL might trigger a Jinja2 rendering error, in which case the URL would need to be properly escaped.

New Features

Plugins Framework Extensions (#8333)

NetBox's plugins framework has been extended considerably in this release. Additions include:

  • Officially-supported generic view classes for common CRUD operations:
    • ObjectView
    • ObjectEditView
    • ObjectDeleteView
    • ObjectListView
    • BulkImportView
    • BulkEditView
    • BulkDeleteView
  • The NetBoxModel base class, which enables various NetBox features, including:
    • Change logging
    • Custom fields
    • Custom links
    • Custom validation
    • Export templates
    • Journaling
    • Tags
    • Webhooks
  • Four base form classes for manipulating objects via the UI:
    • NetBoxModelForm
    • NetBoxModelCSVForm
    • NetBoxModelBulkEditForm
    • NetBoxModelFilterSetForm
  • The NetBoxModelFilterSet base class for plugin filter sets
  • The NetBoxTable base class for rendering object tables with django-tables2, as well as various custom column classes
  • Function-specific templates (for generic views)
  • Various custom template tags and filters
  • NetBoxModelViewSet and several base serializer classes now provide enhanced REST API functionality
  • Plugins can now extend NetBox's GraphQL API with their own schema

No breaking changes to previously supported components have been introduced in this release. However, plugin authors are encouraged to audit their existing code for misuse of unsupported components, as much of NetBox's internal code base has been reorganized.

Modules & Module Types (#7844)

Several new models have been added to represent field-replaceable device modules, such as line cards installed within a chassis-based switch or router. Similar to devices, each module is instantiated from a user-defined module type, and can have components (interfaces, console ports, etc.) associated with it. These components become available to the parent device once the module has been installed within a module bay. This provides a convenient mechanism to effect the addition and deletion of device components as modules are installed and removed.

Automatic renaming of module components is also supported. When a new module is created, any occurrence of the string {module} in a component name will be replaced with the position of the module bay into which the module is being installed.

As with device types, the NetBox community offers a selection of curated real-world module type definitions in our device type library. These YAML files can be imported directly to NetBox for your convenience.

Custom Object Fields (#7006)

Two new types of custom field have been introduced: object and multi-object. These can be used to associate an object in NetBox with some other arbitrary object(s) regardless of its type. For example, you might create a custom field named primary_site on the tenant model so that each tenant can have particular site designated as its primary. The multi-object custom field type allows for the assignment of multiple objects of the same type.

Custom field object assignment is fully supported in the REST API, and functions similarly to built-in foreign key relations. Nested representations are provided automatically for each custom field object.

Custom Status Choices (#8054)

Custom choices can be now added to most object status fields in NetBox. This is done by defining the FIELD_CHOICES configuration parameter to map field identifiers to an iterable of custom choices an (optionally) colors. These choices are populated automatically when NetBox initializes. For example, the following configuration will add three custom choices for the site status field, each with a designated color:

FIELD_CHOICES = {
    'dcim.Site.status': (
        ('foo', 'Foo', 'red'),
        ('bar', 'Bar', 'green'),
        ('baz', 'Baz', 'blue'),
    )
}

This will replace all default choices for this field with those listed. If instead the intent is to extend the set of default choices, this can be done by appending a plus sign (+) to the end of the field identifier. For example, the following will add a single extra choice while retaining the defaults provided by NetBox:

FIELD_CHOICES = {
    'dcim.Site.status+': (
        ('fubar', 'FUBAR', 'red'),
    )
}

Improved User Preferences (#7759)

A robust new mechanism for managing user preferences is included in this release. The user preferences form has been improved for better usability, and administrators can now define default preferences for all users with the DEFAULT_USER_PREFERENCES configuration parameter. For example, this can be used to define the columns which appear by default in a table:

DEFAULT_USER_PREFERENCES = {
    'tables': {
        'IPAddressTable': {
            'columns': ['address', 'status', 'created', 'description']
        }
    }
}

Users can adjust their own preferences under their user profile. A complete list of supported preferences is available in NetBox's developer documentation.

Inventory Item Roles (#3087)

A new model has been introduced to represent functional roles for inventory items, similar to device roles. The assignment of roles to inventory items is optional.

Inventory Item Templates (#8118)

Inventory items can now be templatized on a device type similar to other components (such as interfaces or console ports). This enables users to better pre-model fixed hardware components such as power supplies or hard disks.

Inventory item templates can be arranged hierarchically within a device type, and may be assigned to other templated components. These relationships will be mirrored when instantiating inventory items on a newly-created device (see #7846). For example, if defining an optic assigned to an interface template on a device type, the instantiated device will mimic this relationship between the optic and interface.

Service Templates (#1591)

A new service template model has been introduced to assist in standardizing the definition and association of applications with devices and virtual machines. As an alternative to manually defining a name, protocol, and port(s) each time a service is created, a user now has the option of selecting a pre-defined template from which these values will be populated.

Automatic Provisioning of Next Available VLANs (#2658)

A new REST API endpoint has been added at /api/ipam/vlan-groups/<id>/available-vlans/. A GET request to this endpoint will return a list of available VLANs within the group. A POST request can be made specifying the name(s) of one or more VLANs to create within the group, and their VLAN IDs will be assigned automatically from the available pool.

Where it is desired to limit the range of available VLANs within a group, users can define a minimum and/or maximum VLAN ID per group (see #8168).

Enhancements

  • #5429 - Enable toggling the placement of table pagination controls
  • #6954 - Remember users' table ordering preferences
  • #7650 - Expose AUTH_PASSWORD_VALIDATORS setting to enforce password validation for local accounts
  • #7679 - Add actions menu to all object tables
  • #7681 - Add service_id field for provider networks
  • #7784 - Support cluster type assignment for config contexts
  • #7846 - Enable associating inventory items with device components
  • #7852 - Enable the assignment of interfaces to VRFs
  • #7853 - Add speed and duplex fields to device interface model
  • #8168 - Add min_vid and max_vid fields to VLAN group
  • #8295 - Jinja2 rendering is now supported for webhook URLs
  • #8296 - Allow disabling custom links
  • #8307 - Add data_type indicator to REST API serializer for custom fields
  • #8463 - Change the created field on all change-logged models from date to datetime
  • #8496 - Enable assigning multiple ASNs to a provider
  • #8572 - Add a pre_run() method for reports
  • #8593 - Add a link field for contacts
  • #8649 - Enable customization of configuration module using NETBOX_CONFIGURATION environment variable
  • #9006 - Enable custom fields, custom links, and tags for journal entries

Bug Fixes (From Beta2)

  • #8658 - Fix display of assigned components under inventory item lists
  • #8838 - Fix FieldError exception during global search
  • #8845 - Correct default ASN formatting in table
  • #8869 - Fix NoReverseMatch exception when displaying tag w/assignments
  • #8872 - Enable filtering by custom object fields
  • #8970 - Permit nested inventory item templates on device types
  • #8976 - Add missing object_type field on CustomField REST API serializer
  • #8978 - Fix instantiation of front ports when provisioning a module
  • #9007 - Fix FieldError exception when instantiating a device type with nested inventory items

Other Changes

  • #7731 - Require Python 3.8 or later
  • #7743 - Remove legacy ASN field from site model
  • #7748 - Remove legacy contact fields from site model
  • #8031 - Remove automatic redirection of legacy slug-based URLs
  • #8195, #8454 - Use 64-bit integers for all primary keys
  • #8509 - CSRF_TRUSTED_ORIGINS is now a discrete configuration parameter (rather than being populated from ALLOWED_HOSTS)
  • #8684 - Change custom link template context variable obj to object (backward-compatible)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/9041 **Author:** [@jeremystretch](https://github.com/jeremystretch) **Created:** 4/5/2022 **Status:** ✅ Merged **Merged:** 4/5/2022 **Merged by:** [@jeremystretch](https://github.com/jeremystretch) **Base:** `master` ← **Head:** `develop` --- ### 📝 Commits (10+) - [`ae3c871`](https://github.com/netbox-community/netbox/commit/ae3c8714386497c408370f0ae80e0d23ef48b8b2) Merge pull request #8186 from netbox-community/8118-inventoryitem-template - [`9f53497`](https://github.com/netbox-community/netbox/commit/9f53497e391f29961bda990eda88a8a943e5c96f) Clean up & expand button color choices - [`8e69961`](https://github.com/netbox-community/netbox/commit/8e699617448757f1b10a0befce7290b678f50494) Fix CustomLinkButtonClassChoices references in tests - [`0978777`](https://github.com/netbox-community/netbox/commit/0978777eecb7a29ccc4c631b2b5be09c25b7c02d) Merge v3.1.4 - [`fa1e28e`](https://github.com/netbox-community/netbox/commit/fa1e28e860c4bdb3e585a968bd248a2ac666e1f6) Initial work on #7006 - [`954d811`](https://github.com/netbox-community/netbox/commit/954d81147e7d65ad099fc122ab2ea790b0eb0e0b) Reindex migrations - [`88ac0f5`](https://github.com/netbox-community/netbox/commit/88ac0f5d3409d0727aef5518c3632cd6b9383732) Work on #6221 - Make templatetags safe for consumption when using plugins and update ButtonColumn to use viewname helper. - [`271b7ad`](https://github.com/netbox-community/netbox/commit/271b7adeb830eaafa6bb117c49aee3ceff7b1adc) Extend to support the assignment of multiple objects per field - [`85c0637`](https://github.com/netbox-community/netbox/commit/85c06372ffe04f0fbb4ac6c05394bc1f819785d0) Fix bulk editing for custom object fields - [`7aa1fab`](https://github.com/netbox-community/netbox/commit/7aa1fabbd7f4117242d2bdc564fd4dee31182edb) Fix tests ### 📊 Changes **498 files changed** (+20501 additions, -11383 deletions) <details> <summary>View changed files</summary> 📝 `.github/ISSUE_TEMPLATE/bug_report.yaml` (+1 -1) 📝 `.github/ISSUE_TEMPLATE/feature_request.yaml` (+1 -1) 📝 `.github/workflows/ci.yml` (+4 -3) ➕ `.readthedocs.yaml` (+10 -0) 📝 `base_requirements.txt` (+11 -2) 📝 `docs/configuration/dynamic-settings.md` (+16 -0) 📝 `docs/configuration/index.md` (+6 -1) 📝 `docs/configuration/optional-settings.md` (+92 -0) 📝 `docs/core-functionality/device-types.md` (+1 -0) 📝 `docs/core-functionality/devices.md` (+1 -0) ➕ `docs/core-functionality/modules.md` (+4 -0) 📝 `docs/core-functionality/services.md` (+1 -0) 📝 `docs/customization/reports.md` (+1 -1) 📝 `docs/development/adding-models.md` (+1 -1) 📝 `docs/development/getting-started.md` (+38 -19) 📝 `docs/development/release-checklist.md` (+1 -1) 📝 `docs/development/user-preferences.md` (+8 -5) 📝 `docs/index.md` (+1 -1) 📝 `docs/installation/3-netbox.md` (+7 -12) 📝 `docs/installation/index.md` (+1 -1) _...and 80 more files_ </details> ### 📄 Description ### Breaking Changes * Automatic redirection of legacy slug-based URL paths has been removed. URL-based slugs were changed to use numeric IDs in v2.11.0. * The `asn` field has been removed from the site model. Please replicate any site ASN assignments to the ASN model introduced in NetBox v3.1 prior to upgrading. * The `asn` query filter for sites now matches against the AS number of assigned ASN objects. * The `contact_name`, `contact_phone`, and `contact_email` fields have been removed from the site model. Please replicate any data remaining in these fields to the contact model introduced in NetBox v3.1 prior to upgrading. * The `created` field of all change-logged models now conveys a full datetime object, rather than only a date. (Previous date-only values will receive a timestamp of 00:00.) While this change is largely unconcerning, strictly-typed API consumers may need to be updated. * A `pre_run()` method has been added to the base Report class. Although unlikely to affect most installations, you may need to alter any reports which already use this name for a method. * Webhook URLs now support Jinja2 templating. Although this is unlikely to introduce any issues, it's possible that an unusual URL might trigger a Jinja2 rendering error, in which case the URL would need to be properly escaped. ### New Features #### Plugins Framework Extensions ([#8333](https://github.com/netbox-community/netbox/issues/8333)) NetBox's plugins framework has been extended considerably in this release. Additions include: * Officially-supported generic view classes for common CRUD operations: * `ObjectView` * `ObjectEditView` * `ObjectDeleteView` * `ObjectListView` * `BulkImportView` * `BulkEditView` * `BulkDeleteView` * The `NetBoxModel` base class, which enables various NetBox features, including: * Change logging * Custom fields * Custom links * Custom validation * Export templates * Journaling * Tags * Webhooks * Four base form classes for manipulating objects via the UI: * `NetBoxModelForm` * `NetBoxModelCSVForm` * `NetBoxModelBulkEditForm` * `NetBoxModelFilterSetForm` * The `NetBoxModelFilterSet` base class for plugin filter sets * The `NetBoxTable` base class for rendering object tables with `django-tables2`, as well as various custom column classes * Function-specific templates (for generic views) * Various custom template tags and filters * `NetBoxModelViewSet` and several base serializer classes now provide enhanced REST API functionality * Plugins can now extend NetBox's GraphQL API with their own schema No breaking changes to previously supported components have been introduced in this release. However, plugin authors are encouraged to audit their existing code for misuse of unsupported components, as much of NetBox's internal code base has been reorganized. #### Modules & Module Types ([#7844](https://github.com/netbox-community/netbox/issues/7844)) Several new models have been added to represent field-replaceable device modules, such as line cards installed within a chassis-based switch or router. Similar to devices, each module is instantiated from a user-defined module type, and can have components (interfaces, console ports, etc.) associated with it. These components become available to the parent device once the module has been installed within a module bay. This provides a convenient mechanism to effect the addition and deletion of device components as modules are installed and removed. Automatic renaming of module components is also supported. When a new module is created, any occurrence of the string `{module}` in a component name will be replaced with the position of the module bay into which the module is being installed. As with device types, the NetBox community offers a selection of curated real-world module type definitions in our [device type library](https://github.com/netbox-community/devicetype-library). These YAML files can be imported directly to NetBox for your convenience. #### Custom Object Fields ([#7006](https://github.com/netbox-community/netbox/issues/7006)) Two new types of custom field have been introduced: object and multi-object. These can be used to associate an object in NetBox with some other arbitrary object(s) regardless of its type. For example, you might create a custom field named `primary_site` on the tenant model so that each tenant can have particular site designated as its primary. The multi-object custom field type allows for the assignment of multiple objects of the same type. Custom field object assignment is fully supported in the REST API, and functions similarly to built-in foreign key relations. Nested representations are provided automatically for each custom field object. #### Custom Status Choices ([#8054](https://github.com/netbox-community/netbox/issues/8054)) Custom choices can be now added to most object status fields in NetBox. This is done by defining the [`FIELD_CHOICES`](../configuration/optional-settings.md#field_choices) configuration parameter to map field identifiers to an iterable of custom choices an (optionally) colors. These choices are populated automatically when NetBox initializes. For example, the following configuration will add three custom choices for the site status field, each with a designated color: ```python FIELD_CHOICES = { 'dcim.Site.status': ( ('foo', 'Foo', 'red'), ('bar', 'Bar', 'green'), ('baz', 'Baz', 'blue'), ) } ``` This will replace all default choices for this field with those listed. If instead the intent is to _extend_ the set of default choices, this can be done by appending a plus sign (`+`) to the end of the field identifier. For example, the following will add a single extra choice while retaining the defaults provided by NetBox: ```python FIELD_CHOICES = { 'dcim.Site.status+': ( ('fubar', 'FUBAR', 'red'), ) } ``` #### Improved User Preferences ([#7759](https://github.com/netbox-community/netbox/issues/7759)) A robust new mechanism for managing user preferences is included in this release. The user preferences form has been improved for better usability, and administrators can now define default preferences for all users with the [`DEFAULT_USER_PREFERENCES`](../configuration/dynamic-settings.md##default_user_preferences) configuration parameter. For example, this can be used to define the columns which appear by default in a table: ```python DEFAULT_USER_PREFERENCES = { 'tables': { 'IPAddressTable': { 'columns': ['address', 'status', 'created', 'description'] } } } ``` Users can adjust their own preferences under their user profile. A complete list of supported preferences is available in NetBox's [developer documentation](../development/user-preferences.md). #### Inventory Item Roles ([#3087](https://github.com/netbox-community/netbox/issues/3087)) A new model has been introduced to represent functional roles for inventory items, similar to device roles. The assignment of roles to inventory items is optional. #### Inventory Item Templates ([#8118](https://github.com/netbox-community/netbox/issues/8118)) Inventory items can now be templatized on a device type similar to other components (such as interfaces or console ports). This enables users to better pre-model fixed hardware components such as power supplies or hard disks. Inventory item templates can be arranged hierarchically within a device type, and may be assigned to other templated components. These relationships will be mirrored when instantiating inventory items on a newly-created device (see [#7846](https://github.com/netbox-community/netbox/issues/7846)). For example, if defining an optic assigned to an interface template on a device type, the instantiated device will mimic this relationship between the optic and interface. #### Service Templates ([#1591](https://github.com/netbox-community/netbox/issues/1591)) A new service template model has been introduced to assist in standardizing the definition and association of applications with devices and virtual machines. As an alternative to manually defining a name, protocol, and port(s) each time a service is created, a user now has the option of selecting a pre-defined template from which these values will be populated. #### Automatic Provisioning of Next Available VLANs ([#2658](https://github.com/netbox-community/netbox/issues/2658)) A new REST API endpoint has been added at `/api/ipam/vlan-groups/<id>/available-vlans/`. A GET request to this endpoint will return a list of available VLANs within the group. A POST request can be made specifying the name(s) of one or more VLANs to create within the group, and their VLAN IDs will be assigned automatically from the available pool. Where it is desired to limit the range of available VLANs within a group, users can define a minimum and/or maximum VLAN ID per group (see [#8168](https://github.com/netbox-community/netbox/issues/8168)). ### Enhancements * [#5429](https://github.com/netbox-community/netbox/issues/5429) - Enable toggling the placement of table pagination controls * [#6954](https://github.com/netbox-community/netbox/issues/6954) - Remember users' table ordering preferences * [#7650](https://github.com/netbox-community/netbox/issues/7650) - Expose `AUTH_PASSWORD_VALIDATORS` setting to enforce password validation for local accounts * [#7679](https://github.com/netbox-community/netbox/issues/7679) - Add actions menu to all object tables * [#7681](https://github.com/netbox-community/netbox/issues/7681) - Add `service_id` field for provider networks * [#7784](https://github.com/netbox-community/netbox/issues/7784) - Support cluster type assignment for config contexts * [#7846](https://github.com/netbox-community/netbox/issues/7846) - Enable associating inventory items with device components * [#7852](https://github.com/netbox-community/netbox/issues/7852) - Enable the assignment of interfaces to VRFs * [#7853](https://github.com/netbox-community/netbox/issues/7853) - Add `speed` and `duplex` fields to device interface model * [#8168](https://github.com/netbox-community/netbox/issues/8168) - Add `min_vid` and `max_vid` fields to VLAN group * [#8295](https://github.com/netbox-community/netbox/issues/8295) - Jinja2 rendering is now supported for webhook URLs * [#8296](https://github.com/netbox-community/netbox/issues/8296) - Allow disabling custom links * [#8307](https://github.com/netbox-community/netbox/issues/8307) - Add `data_type` indicator to REST API serializer for custom fields * [#8463](https://github.com/netbox-community/netbox/issues/8463) - Change the `created` field on all change-logged models from date to datetime * [#8496](https://github.com/netbox-community/netbox/issues/8496) - Enable assigning multiple ASNs to a provider * [#8572](https://github.com/netbox-community/netbox/issues/8572) - Add a `pre_run()` method for reports * [#8593](https://github.com/netbox-community/netbox/issues/8593) - Add a `link` field for contacts * [#8649](https://github.com/netbox-community/netbox/issues/8649) - Enable customization of configuration module using `NETBOX_CONFIGURATION` environment variable * [#9006](https://github.com/netbox-community/netbox/issues/9006) - Enable custom fields, custom links, and tags for journal entries ### Bug Fixes (From Beta2) * [#8658](https://github.com/netbox-community/netbox/issues/8658) - Fix display of assigned components under inventory item lists * [#8838](https://github.com/netbox-community/netbox/issues/8838) - Fix FieldError exception during global search * [#8845](https://github.com/netbox-community/netbox/issues/8845) - Correct default ASN formatting in table * [#8869](https://github.com/netbox-community/netbox/issues/8869) - Fix NoReverseMatch exception when displaying tag w/assignments * [#8872](https://github.com/netbox-community/netbox/issues/8872) - Enable filtering by custom object fields * [#8970](https://github.com/netbox-community/netbox/issues/8970) - Permit nested inventory item templates on device types * [#8976](https://github.com/netbox-community/netbox/issues/8976) - Add missing `object_type` field on CustomField REST API serializer * [#8978](https://github.com/netbox-community/netbox/issues/8978) - Fix instantiation of front ports when provisioning a module * [#9007](https://github.com/netbox-community/netbox/issues/9007) - Fix FieldError exception when instantiating a device type with nested inventory items ### Other Changes * [#7731](https://github.com/netbox-community/netbox/issues/7731) - Require Python 3.8 or later * [#7743](https://github.com/netbox-community/netbox/issues/7743) - Remove legacy ASN field from site model * [#7748](https://github.com/netbox-community/netbox/issues/7748) - Remove legacy contact fields from site model * [#8031](https://github.com/netbox-community/netbox/issues/8031) - Remove automatic redirection of legacy slug-based URLs * [#8195](https://github.com/netbox-community/netbox/issues/8195), [#8454](https://github.com/netbox-community/netbox/issues/8454) - Use 64-bit integers for all primary keys * [#8509](https://github.com/netbox-community/netbox/issues/8509) - `CSRF_TRUSTED_ORIGINS` is now a discrete configuration parameter (rather than being populated from `ALLOWED_HOSTS`) * [#8684](https://github.com/netbox-community/netbox/issues/8684) - Change custom link template context variable `obj` to `object` (backward-compatible) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 22:27:20 +01:00
adam closed this issue 2025-12-29 22:27:20 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#13425
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?