chore(deps): update ghcr.io/nautobot/nautobot docker tag to v2.2.2

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/nautobot/nautobot	minor	2.1.9-py3.11 -> 2.2.2-py3.11

---

Release Notes

nautobot/nautobot (ghcr.io/nautobot/nautobot)

v2.2.2: - 2024-04-18

Compare Source

What's Changed

Security

• #​5579 - Updated sqlparse to 0.5.0 to fix GHSA-2m57-hf25-phgg. This is not a direct dependency so it will not auto-update when upgrading Nautobot. Please be sure to update your local environment.

Added

• #​2459 - Added nautobot.extras.utils.bulk_delete_with_bulk_change_logging helper function for improving performance on bulk delete.
• #​2459 - Added nautobot.extras.context_managers.deferred_change_logging_for_bulk_operation context manager for improving performance on bulk update.

Changed

• #​2459 - Improved performance of bulk-edit and bulk-delete UI operations by refactoring change logging logic.
• #​5568 - Added hyperlink to the total device count number under device family.
• #​5589 - Fixed an invalid Javascript operator in the LLDP neighbor view.

Fixed

• #​5580 - Fixed bugs when assigning a VLAN to an Interface related to the recently introduced many-to-many relationship between VLANs and Locations.
• #​5592 - Fixed plugins not loading when using Gunicorn.

Documentation

• #​5583 - Re-added release note content for v1.6.16 through v1.6.18.

Housekeeping

• #​5590 - Fixed upstream testing workflows showing successful when one of the steps fail.

Contributors

• @​HanlinMiao
• @​gsnider2195
• @​abates
• @​ericchou1

Full Changelog: nautobot/nautobot@v2.2.1...v2.2.2

v2.2.1: - 2024-04-15

Compare Source

What's Changed

Security

• #​5521 - Updated Pillow dependency to ~10.3.0 to address CVE-2024-28219.
• #​5543 - Updated jquery-ui to version 1.13.2 due to CVE-2022-31160.
• #​5561 - Updated idna to 3.7 due to CVE-2024-3651. This is not a direct dependency so will not auto-update when upgrading. Please be sure to upgrade your local environment.

Added

• #​1631 - Added change logging for custom field background tasks.
• #​5009 - Added the option to filter objects with select/multi-select custom fields based on the UUID of the defined custom field choice(s), for example /api/dcim/locations/?cf_multiselect=1ea9237c-3ba7-4985-ba7e-6fd9e9bff813 as an alternative to /api/dcim/locations/?cf_multiselect=some-choice-value.
• #​5493 - Added a configuration setting METRICS_DISABLED_APPS to disable app metrics for specific apps.
• #​5540 - Added total devices count to device family detail page.

Changed

• #​5274 - Added a setting that changes all rack unit numbers to display a minimum of two digits in rack elevations.

Fixed

• #​5469 - Fixed contacts and teams not being included in the global search.
• #​5489 - Fixed REST API for Contact and Team incorrectly marking the phone and email fields as mandatory.
• #​5502 - Fixed off-by-one error in generic filter testing helper BaseFilterTestCase.get_filterset_test_values.
• #​5511 - Fixed contact tab disappearing when accessing dynamic groups tab.
• #​5515 - Fixed javascript exception thrown in the Device LLDP neighbors view for neighbors without configured devices/interfaces.
• #​5527 - Fixed incorrect "members" links in Virtual Chassis list view.
• #​5531 - Re-added nautobot.setup() function mistakenly removed in 2.2.0.

Dependencies

• #​5495 - Changed jsonschema version constraint from >=4.7.0,<4.19.0 to ^4.7.0.
• #​5517 - Updated djangorestframework to ~3.15.1.
• #​5521 - Updated most dependencies to the latest versions available as of 2024-04-01.
• #​5543 - Updated jquery to version 3.7.1.

Documentation

• #​5189 - Added "Model Development Checklist" to the core developer documentation.
• #​5189 - Merged "Extending Models" documentation into the "Model Development Checklist" documentation.
• #​5526 - Fixed doc reference to job cprofile file location.

Housekeeping

• #​5531 - Removed nautobot-server pylint management command from the example_app, as pylint can be invoked directly with an appropriate --init-hook instead.
• #​5547 - Fixed TransactionTestCase inheritance order so that test.client works in test cases using this class.

Contributors

• @​glennmatthews
• @​gsnider2195
• @​jvanderaa
• @​abates
• @​tsm1th
• @​itdependsnetworks
• @​Kircheneer
• @​HanlinMiao
• @​ericchou1

New Contributors

• @​tsm1th made their first contribution in https://github.com/nautobot/nautobot/pull/5508
• @​ericchou1 made their first contribution in https://github.com/nautobot/nautobot/pull/5541

Full Changelog: nautobot/nautobot@v2.2.0...v2.2.1

v2.2.0: - 2024-03-29

Compare Source

What's Changed

Added

Contact and Team Models (#​230)

Contact and Team are models that represent an individual and a group of individuals who can be linked to an object. Contacts and teams store the necessary information (name, phone number, email, and address) to uniquely identify and contact them. They are added to track ownerships of organizational entities and to manage resources more efficiently in Nautobot. Check out the documentation for Contact and Team. There is also a user guide available on how to utilize these models.

A new management command has been introduced to assist with migrating the Location fields contact_name, contact_phone and contact_email to the new Contact and Team models. This command can be invoked with nautobot-server migrate_location_contacts and will present a series of prompts to guide you through migrating Locations that have data in the contact_name, contact_phone, or contact_email fields which are not already associated to a Contact or Team. This command will give you the option to create new Contacts or Teams or, if a similar Contact or Team already exists, to link the Location to the existing Contact or Team. Note that when assigning a Location to an existing Contact or Team that has a blank phone or email field, the value from the Location will be copied to the Contact/Team. After a Location has been associated to a Contact or Team, the contact_name, contact_phone, and contact_email fields will be cleared from the Location.

Controller Model (#​3111)

Controller models have been added to the dcim app. A Controller in Nautobot is an abstraction meant to represent network or SDN (Software-Defined Networking) controllers. These may include, but are not limited to, wireless controllers, cloud-based network management systems, and other forms of central network control mechanisms.

For more details, refer to the user guide for a Controller model, a ControllerManagedDeviceGroup model, or developer documentation for Controllers.

DeviceFamily Model (#​3559)

A Device Family represents a group of related Device Types. A Device Type can be optionally assigned to a Device Family. Each Device Family must have a unique name and may have a description assigned to it.

Jobs Tile View (#​5129)

Job list is now available in two display variants: list and tiles. List is a standard table view with no major changes introduced. Tiles is a new type of view displaying jobs in a two-dimensional grid.

Prefix and VLAN Many Locations (#​4334, #​4412)

The Prefix and VLAN models have replaced their single location foreign-key field with a many-to-many locations field, allowing multiple Locations to be attached to a single Prefix or VLAN. To ensure backwards compatibility with pre-2.2 code, these models now have a location property which can be retrieved or set for the case of a single associated Location, but will raise a MultipleObjectsReturned exception if the Prefix or VLAN in question has more than one associated Location. REST API versions 2.0 and 2.1 similarly still have a location field, while REST API version 2.2 and later replace this with locations.

Software Image File and Software Version models (#​1)

New models have been added for Software Image Files and Software Versions. These models are used to track the software versions of Devices, Inventory Items and Virtual Machines and their associated image files. These models have been ported from the Device Lifecycle Management App and a future update to that app will migrate all existing data from the nautobot_device_lifecycle_mgmt.SoftwareImageLCM and nautobot_device_lifecycle_mgmt.SoftwareLCM models to the dcim.SoftwareImageFile and dcim.SoftwareVersion models added here.

Software Versions must be associated to a Platform. Software Image Files must be associated to one Software Version and may be associated to one or more Device Types. Devices, Inventory Items and Virtual Machines may be associated to one Software Version to track their current version. See the documentation for Software Image File and Software Version. There is also a user guide with instructions on how to create these models.

Syntax Highlighting (#​5098)

Language syntax highlighting for GraphQL, JSON, XML and YAML is now supported in the UI via JavaScript. To enable the feature, a code snippet has to be wrapped in the following HTML structure:

<pre><code class="language-{graphql,json,xml,yaml}">...</code></pre>

render_json and render_yaml template filters default to this new behavior with an optional opt-out syntax_highlight=False arg.

Changed

Data Imports as a System Job (#​5064)

The CSV import functionality for all models has been changed from a synchronous operation to an asynchronous background task (system Job). As a result, imports of large CSV files will no longer fail due to browser timeout.

!!! tip
Users now must have the run action permission for extras > job (specifically the nautobot.core.jobs.ImportObjects Job) in order to import objects, in addition to the normal add permissions for the object type being imported.

Plugin to App Renames (#​5341)

Installed Plugins view has been renamed to Installed Apps. Plugin terminologies in Installed Plugins (now Installed Apps) view and dependent views have been changed to App throughout. Plugin references in documentation (excluding old release-notes) have been replaced by App. Plugins navigation menu has been renamed to Apps.

Standardization of max_length on all Charfields (#​2906)

Model CharFields' max_length attributes have been standardized globally to have at least 255 characters except where a shorter max_length is explicitly justified.

Full Changelog: nautobot/nautobot@v2.1.9...v2.2.0

Contributors

• @​bradh11
• @​snaselj
• @​edwardtheharris
• @​gsnider2195
• @​timizuoebideri1
• @​abates
• @​mzbroch
• @​glennmatthews
• @​lampwins
• @​HanlinMiao
• @​whitej6
• @​norbert-mieczkowski-codilime
• @​gertzakis

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: charts/nautobot/values.yaml

Post-upgrade command 'scripts/update_version.sh "{{{prTitle}}}"' has not been added to the allowed list in allowedPostUpgradeCommands

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.