docs/release-notes/version-4.4.md
ValueError exception when saving a site with an assigned prefixdevicetype_count from nested manufacturer to correct OpenAPI schemaparent_bay during device bulk import when tags are presentAttributeError exception triggered by event rules associated with an object that supports file attachmentsmodule field on ModuleBayon_delete=RESTRICT the same as CASCADErear_port_id{module} resolution of components of child modulesdata_source & data_file when bulk import config templatesTypeError exception when bulk renaming unnamed devicesauto_sync_enabled field in bulk edit formsvc_position of all former membersassigned and primary boolean filters for MAC addressesis_oob & is_primary fields under IP address bulk importAttributeError exception raised by the object changes REST API endpointFieldError exception when attempting to sort permissions list by actions<app>.<model> format matching POST requestsIntegerRangeSerializerMAX_PAGE_SIZE value/) for the global search fieldSENTRY_CONFIG configuration parameterfacility field to bulk edit forms for sites and locationsHttpOnly flag for CSRF cookiedeserialize_object() utilitykind filter for interfaces in GraphQL APIValueError complaining of missing scope when bulk importing wireless LANsAttributeError exception on background jobs with no request IDdistinct() on device/VM queryset when fetching config context dataMost bulk operations, such as the import, modification, or deletion of objects can now be executed as a background job. This frees the user to continue working in NetBox while the bulk operation is processed. Once completed, the user will be notified of the job's result.
A dedicated logging mechanism has been implemented for background jobs. Jobs can now easily record log messages by calling e.g. self.logger.info("Log message") under the run() method. These messages are displayed along with the job's resulting data. Supported log levels include DEBUG, INFO, WARNING, and ERROR.
When creating, editing, or deleting objects in NetBox, users now have the option of providing a short message explaining the change. This message will be recorded on the resulting changelog records for all affected objects.
A new ConfigContextProfile model has been introduced to support JSON schema validation for config context data. If a validation schema has been defined for a profile, all config contexts assigned to it will have their data validated against the schema whenever a change is made. (The assignment of a config context to a profile is optional.)
HOSTNAME configuration parameter to override the system hostname reported by NetBoxstatus field for rack reservations/api/status/ REST API endpoint now includes the system hostnameObjectAction/api/core/nbshell management commandchangelog_message for write operations. If provided, this message will be attached to the changelog record resulting from the change (if successful)./api/status/ endpoint now includes the system hostname./api/extras/object-types/ endpoint is now available at /api/core/object-types/. (The original endpoint will be removed in NetBox v4.5.)/api/core/object-types/ endpoint has been expanded to include the following read-only fields:
app_namemodel_namemodel_name_pluralis_plugin_modelrest_api_endpointdescription/api/extras/config-context-profiles/ endpointlog_entries array fieldtx_power field now accepts negative valuesstatus choice fieldparent foreign key field to support nestingprofile foreign key fielddescription field