This document describes all new features and changes in Nautobot 1.1.
If you are a user migrating from NetBox to Nautobot, please refer to the "Migrating from NetBox" documentation.
Computed fields offers users the ability to create read-only custom fields using existing data already stored in the database. Users define Jinja2 templates that populate the value of these fields. Computed fields are available on all data models that currently support custom fields.
While config contexts allow for arbitrary data structures to be stored within Nautobot, at scale it is desirable to apply validation constraints to that data to ensure its consistency and to avoid data entry errors. To service this need, Nautobot supports optionally backing config contexts with JSON Schemas for validation. These schema are managed via the config context schema model and are optionally linked to config context instances, in addition to devices and virtual machines for the purpose of validating their local context data. Please see the docs for more details.
Just like config contexts, config context JSON schemas can optionally be managed via a Git repository.
Applications and plugins can now define tabs, groups, items and buttons in the navigation menu. Using navigation objects a developer can add items to any section of the navigation using key names and weight values. Please see Application Registry for more details.
MySQL 8.x is now fully supported as a database backend!
The installation and configuration guides have been revised to include MySQL. If you prefer MySQL or it is more easily supported in your environment, configuring Nautobot to use MySQL is as easy as changing value of
ENGINE in your
DATABASES setting to point to
django.db.backends.mysql and installing the MySQL Python driver using
pip3 install nautobot[mysql].
NAUTOBOT_DB_ENGINE environment variable has been added to allow for specifying the desired database engine at runtime without needing to modify your
nautobot_config.py. Please see the configuration guide on
DATABASES for more details on how to configure Nautobot to use MySQL.
Plugin Defined Jinja2 Filters¶
Plugins can now define custom Jinja2 filters to be used when rendering templates defined within computed fields or custom links. To register your own filters, you may add a
jinja_filters.py to your plugin and any filters defined there will be automatically registered and globally usable.
Please see the plugin development documentation on including Jinja2 filters to get started.
Jobs may be optionally marked as read only by setting the
read_only = True meta attribute. This prevents the job from making any changes to nautobot data and suppresses certain log messages. Read only jobs can be a great way to safely develop new jobs, and for working with reporting use cases. Please see the Jobs documentation for more details.
Saved GraphQL queries offers a new model where reusable queries can be stored in Nautobot. New views for managing saved queries are available; additionally, the GraphiQL interface has been augmented to allow populating the interface from a saved query, editing and saving new queries.
Saved queries can easily be imported into the GraphiQL interface by using the new navigation tab located on the right side of the navbar. Inside the new tab are also buttons for editing and saving queries directly into Nautobot's databases.
Additionally, two new GraphQL utility functions have been added to allow easy access to the GraphQL system from source code. Both functions can be imported from
execute_query(): Runs string as a query against GraphQL.
execute_saved_query(): Execute a saved query from Nautobot database.
Celery has been introduced to eventually replace RQ for executing background tasks within Nautobot. All Nautobot core usage of RQ has been migrated to use Celery.
Custom background tasks implemented by plugins are not part of Nautobot core functions
Prior to version 1.1.0, Nautobot utilized RQ as the primary background task worker. As of Nautobot 1.1.0, RQ is now deprecated. RQ and the
@job decorator for custom tasks are still supported for now, but will no longer be documented, and support for RQ will be removed in a future release.
RQ support for custom tasks was not removed in order to give plugin authors time to migrate, however, to continue to utilize advanced Nautobot features such as Git repository synchronization, webhooks, jobs, etc. you must migrate your
nautobot-worker deployment from RQ to Celery.
Please see the section on migrating to Celery from RQ for more information on how to easily migrate your deployment.
If you are running plugins that use background tasks requiring the RQ worker, you will need to run both the RQ and Celery workers concurrently until the plugins are converted to use the Celery worker. See the Migrating to Celery from RQ for details.
uwsgi.ini provided in earlier versions of the Nautobot documentation was missing a recommendation to include the configuration
http-keepalive = 1 which enables support for HTTP/1.1 keep-alive headers.
If you are upgrading from an earlier version of Nautobot (including 1.1.0) you should check your
uwsgi.ini and ensure that it contains this important configuration line.
- #1093 - Improved REST API performance by adding caching of serializer "opt-in fields".
- #263 - Added a link in the Docker deployment guide to the Nautobot Docker Compose repository.
- #931 - Added support for direct upload of CSV files as an alternative to copy-pasting CSV text into a form field. (Partially based on NetBox #6561)
- #953 - Added option to use MySQL in the docker-compose development environment
- #954 - Added documentation for migrating from PostgreSQL to MySQL, improved documentation as to recommended MySQL database configuration.
- #989 - Added
NestedJobResultSerializerfor the REST API.
- #1019 - Added GitHub action to redeploy the Nautobot sandbox on pushes to
- #1025 - Added reference documentation for how to hide navigation menu items with no permissions.
- #1031 - Added a troubleshooting note around the combination of RedHat/CentOS, uWSGI, and static files.
- #1057 - Added GitHub action to automatically push Docker images to
- #555 - Fixed
- #567 - Fixed incorrect GraphQL schema generation for
_custom_field_datawhen certain plugins are installed.
- #733 - A Job erroring out early in initialization could result in its associated JobResult staying in Pending state indefinitely.
- #816 - Fixed
AttributeErrorreported when viewing a Rack with certain associated power configurations.
- #948 - Fixed advanced logging example to use
- #970 - Clarified documentation around config context definition in Git repositories.
- #981 - Fixed incorrect handling of missing custom fields in the
- #986 - Fixed
TemplateDoesNotExistexception when running a Job containing a
- #991 - Fixed incorrect logging when importing ConfigContextSchemas from Git.
- #993 - Fixed incorrect
gitcommand when refreshing a previously checked out repository.
- #1023 - Removed invalid link in "Deploying Nautobot" documentation.
- #998 - Update
mkdocsdependency to avoid a potential path-traversal vulnerability; note that mkdocs is only used in development and is not a production deployment dependency of Nautobot.
- #623 - Git repository sync logs now include the commit hash that was synchronized to.
- #728 - Added
SOCIAL_AUTH_BACKEND_PREFIXconfiguration setting to support custom authentication backends.
- #861 - Bulk editing of devices can now update their site, rack, and rack-group assignments.
- #949 - Added documentation note about using
MAINTENANCE_MODEin combination with LDAP.
- #956 - Switched CI from Travis to GitHub Actions.
- #964 - Updated README.md build status badge to show GitHub status.
- #944 - Jobs that commit changes to the database could not be invoked successfully from the
- #955 - REST API endpoint for syncing Git repositories was still checking for RQ workers instead of Celery workers.
- #969 - IPv6 prefixes such as
::1/128were not being treated correctly.
- #939 - Nautobot views now default to
X-Frame-Options: DENYrather than
X-Frame-Options: SAMEORIGIN, with the exception of the rack-elevation API view (
/api/dcim/rack-elevation/) which specifically requires
X-Frame-Options: SAMEORIGINfor functional reasons.
- #11 - Added tests to verify that plugin models can support webhooks if appropriately decorated with
- #652 - Jobs REST API
runendpoint now can look up ObjectVar references via a dictionary of parameters.
- #755 - Added example showing how to use
django-request-loggingmiddleware to log the user associated with inbound requests.
- #791 - Added support for
NAUTOBOT_DOCKER_SKIP_INITvariable to allow running the Docker container with a read-only database.
- #841 - Added more detailed documentation around defining Relationship filters.
- #850 - Added developer documentation around the installation and use of
mkdocsto locally preview documentation changes.
- #856 - Added more detailed user documentation on how to create an API token.
- #601 - Developer documentation for advanced docker-compose use cases is now a separate file.
- #709 - Computed fields can now have a blank
- #812 - In the GraphiQL interface, the "Queries" dropdown now appears alongside the other GraphiQL interface buttons instead of appearing in the main Nautobot navigation bar.
- #832 - Plugin installation documentation now recommends
nautobot-server post_upgradeinstead of separately running
- #464 - Fixed GraphQL schema generation error when certain custom field names are used.
- #651 - Fixed Jobs validation enforce schema consistently across UI and API.
- #670 - Clarified Jobs documentation regarding how to fail or abort a Job.
- #715 - Fixed display of GraphiQL interface in narrow browser windows.
- #718 - Fixed rendering of long template values in Computed Field detail view.
- #731 - Config context schemas including
formatproperties (such as
"format": "ipv4") are now correctly enforced.
- #779 - Fixed incorrect Tenant display in Prefix "Duplicate Prefixes" table. (Port of two fixes originally from NetBox)
- #809 - Fixed docker-compose file
versionvalues to work correctly with older versions of docker-compose.
- #818 - Database health-check now reports as healthy even when in
- #825 - Removed unnecessary
-Bflag from development Celery worker invocation.
- #830 - Fixed incorrect database migration introduced by #818.
- #845 - Clarified documentation around
- #848 - Fixed stale links to NAPALM documentation
- #893 - Bump Pillow dependency version from 8.2.0 to 8.2.3 to address numerous critical CVE advisories
- #758 - Added documentation about the Job
- #771 - Added examples of various possible logging configurations.
- #773 - Added documentation around enabling Prometheus metrics for database and caching backends.
- #742 - The development environment now respects the setting of the
NAUTOBOT_DEBUGenvironment variable if present.
- #723 - Fixed power draw not providing a
UtilizationDatatype for use in graphing power draw utilization
- #782 - Corrected documentation regarding the use of
- #785 - Fixed plugin loading error when using
- #786 - Fixed
Unknown command: 'post_upgrade'when using
- #789 - Avoid a
NoReverseMatchexception at startup time if an app or plugin defines a nav menu item with an invalid link reference.
- #506 -
nautobot-servernow detects and rejects the misconfiguration of setting
MAINTENANCE_MODEwhile using database-backed session storage (
- #681 - Added an example guide on how to use AWS S3 for hosting static files in production.
- #738 - Added
.gitignoreto prevent local environment variable files from accidentally being committed to Git
- #683 - Fixed slug auto-construction when defining a new ComputedField.
- #725 - Added missing
http-keepalive = 1to recommended
- #727 - Fixed broken REST API endpoint (
/api/extras/graphql-queries/<uuid>/run/) for running saved GraphQL queries.
- #744 - Fixed missing Celery Django fixup that could cause assorted errors when multiple background tasks were run concurrently.
- #746 - Fixed data serialization error when running Jobs that used
- #759 - Corrected backwards add/import links for Power Feed and Power Panel in navigation bar
- #372 - Added support for displaying custom fields in tables used in object list views
- #620 - Config context schemas can now be managed via Git repositories.
- #675 - Update MySQL unicode settings docs to be more visible
- #684 - Renamed
?opt_in_fields=query param to
- #691 - Clarify documentation on RQ to Celery worker migration and running both workers in parallel to help ease migration
- #692 - Clarify plugin development docs on naming of file for custom Jinja2 filters
- #697 - Added
settings.pyand lowered the default
- #363 - Fixed using S3 django-storages backend requires
- #466 - Fixed improper GraphQL schema generation on fields that can be blank but not null (such as
- #663 - Fixed
kombu.exceptions.EncodeErrorwhen trying to execute Jobs using
(Multi)ObjectVarobjects with nested relationships
- #672 - Fixed inheritance of Celery broker/results URL settings for dev/template configs (they can now be defined using Redis env. vars)
- #677 - Revise LDAPS outdated documentation for ignoring TLS cert errors
- #680 - Removed unnecessary warning message when both RQ and Celery workers are present
- #686 - Fixed incorrect permission name for Tags list view in nav menu
- #690 - Fixed Jinja2 dependency version to remain backwards-compatible with Nautobot 1.0.x
- #696 - Fixed inheritance of VRF and Tenant assignment when creating an IPAddress or Prefix under a parent Prefix. (Port of NetBox #5703 and NetBox #6012)
- #698 - Fixed cloning of a computed field object to now carry over required non-unique fields
- #699 - Exceptions such as TypeError are now caught and handled correctly when rendering a computed field.
- #702 - GraphiQL view no longer requires internet access to load libraries.
- #703 - Fixed direct execution of saved GraphQL queries containing double quotes
- #705 - Fixed missing description field from detail view for computed fields
- #717 - Bump Pillow dependency version from 8.1.2 to 8.2.0 to address numerous critical CVE advisories
- #599 - Custom fields are now supported on
- #637 - Implemented a
nautobot-server fix_custom_fieldscommand to manually purge stale custom field data
- #634 - Documentation on plugin capabilities has been clarified.
- #495 - Fixed search for partial IPv4 prefixes/aggregates not finding all matching objects
- #533 - Custom field tasks are now run atomically to avoid stale field data from being saved on objects.
- #554 - Fixed search for partial IPv6 prefixes/aggregates not finding all matching objects
- #569 - Change minimum/maximum allowed values for integer type in Custom Fields to 64-bit
- #600 - The
invoke migratestep is now included in the development getting started guide for Docker workflows
- #617 - Added extra comments to
uwsgi.iniconfig to help with load balancer deployments in Nautobot services documentation
- #626 - Added prefix
override.envexample inside of
- #645 - Updated services troubleshooting docs to include "incorrect string value" fix when using Unicode emojis with MySQL as a database backend
- #653 - Fixed systemd unit file for
nautobot-workerto correctly start/stop/restart
- #661 - Fixed
computed_fieldskey not being included in API response for devices when using
include(for opt-in fields)
- #667 - Fixed various outdated/incorrect places in the documentation for v1.1.0 release.
- #3 - GraphQL queries can now be saved for later execution
- #10 - Added a new "Getting Started in the Web UI" section to the documentation to help new users begin learning how to use Nautobot.
- #17 - MySQL 8.x is now fully supported as a database backend
- #200 - Jobs can be marked as read-only
- #274 - Added config context schemas to optionally validate config and local context data against JSON Schemas
- #297 - Added an anonymous health-checking endpoint at
/health/using, also introducing a
- #485 - Applications can define navbar properties through
- #557 -
Prefixrecords can now be created using /32 (IPv4) and /128 (IPv6) networks. (Port of NetBox #6545)
- #561 - Added autodetection of
export_templatesprovided by Git datasources
- #636 - Added custom fields to
JobResultmodel, with minor changes to job result detail page
- #431 -
ExportTemplaterecords now must have unique
namevalues. This was always the case in NetBox, but was inadvertently un-enforced in earlier versions of Nautobot.
- #460 - Deleting a record now deletes any associated
- #494 - Objects with
statusfields now emit limited choices correctly when performing
OPTIONSmetadata API requests
- #602 - Fixed incorrect requirement to install
tomlPython library before running
- #618 - Fixed typo in release-notes