NetBox v4.3.0-beta1 is now available for testing! #19176
jeremystretch
announced in
Announcements
Replies: 5 comments
-
|
I am unable to perform upgrade from v4.2.7. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
If I read #19002 correctly the end user can define "custom fields" to json schema to provide details to that module. If this is the case please expand this to services as well. Some service specific items I added to a custom field but that custom field also appears on services that do not use that field (although hidden from the ui) buit it does lead to an explosion of custom fields if you have a lot of service types: eg: version: (version of the service) (generic) So you either have to make them generic or add custom fields to all. I'll update my test netbox to this version next week to play around with the module type |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The dropdown menus are not functioning - for example when trying to add a new device the dropdown for Site name is blank even though a site exists. Same goes for device type and device role. UPDATE: the data is actually there but there is weird break in the field which looks to be a missing |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is there no docker hub release for this beta? I can't find it here |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I love the way the IP ranges integrate with the IP address list of the prefix:
Looks promising! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Caution
This is a beta release of NetBox intended for testing and evaluation. Do not use this software in production. Also be aware that no upgrade path is provided to future releases.
The public demo instance is now available for testing.
Breaking Changes
ALLOW_TOKEN_RETRIEVALconfiguration parameter now defaults to False.deviceandvirtual_machineforeign keys on the Service model have been replaced with a genericparentrelationship to support the assignment of services to FHRP groups as well.groupforeign key on the Contact model has been replaced with a many-to-manygroupsfield.modelattribute (usemodelsinstead).New Features
Module Type Profiles & Custom Attributes (#19002)
The new module type profile model enables users to declare custom profiles for module types, with the ability to define custom attributes for each profile according to its functional role. For example, a CPU module type might declare architecture and clock speed attributes; a hard disk profile might declare attributes for type and speed.
Attributes can be declared on each profile using JSON schema, which allows for attributes to be declared as strings (text), integers, decimals, booleans, or choice fields. Profile attributes render as individual form fields when modifying a module type. Several profiles have been included by default to serve as examples, however these may be modified or removed.
Reusable Table Configurations (#14591)
After modifying the displayed columns and/or ordering for a specific object table in the user interface, users now have the option to save that configuration so that it can be reused in the future. Similar to saved filters, table configs can be shared with other users to easily replicate table layouts crafted to serve specific use cases.
Option to Treat IP Ranges as Fully Populated (#9763)
A new
mark_populatedboolean field has been added to the IPRange model. If set to true, NetBox will consider the IP range to be fully populated, and will not permit the creation of individual IP addresses within the range. For example, you might defer the management of an IP range to an external DHCP server, and wish for NetBox to treat the range as a opaque monolithic block for planning and allocation purposes.Hierarchical Device Roles (#18245)
Device roles can now be arranged hierarchically, with one role optionally serving as a parent to one or more child roles. For example, you might wish to create a generic "Server" role for devices with "Application Server" and "Database Server" roles beneath it. A device could then be assigned to any of these three roles.
Periodic Synchronization of Data Sources (#18287)
Data sources can now be configured to synchronize automatically at a specified interval, as indicated by the new
sync_intervalfield. No additional system configuration is necessary to support this functionality; background jobs will be scheduled automatically by the RQ worker process.Proxy Routing (#18627)
User can now declare one or more proxy routers via the
PROXY_ROUTERSconfiguration parameter to control the use of specific proxy servers for various outbound connections. For example, it is now possible to configure NetBox to use different proxies based on the type of outbound traffic or its destination.Enhancements
LOGIN_FORM_HIDDENconfiguration parameterfile_namefield to the export template modelcommentsfield to all nested group models (Region, SiteGroup, Location, ContactGroup, TenantGroup, and WirelessLANGroup)statusfield to the L2VPN model/api/extras/tagged-objects/)weightfield to the Tag model to influence orderingtenantfield to the VLAN group modelstatusfield to the power outlet modelouter_heightfield to the rack & rack type modelsDATABASESandDATABASE_ROUTERSconfiguration parameters to enable defining connections to external databases (e.g. for plugins)Plugins
<head>block via the newplugin_head()method on PluginTemplateExtensionvisibleargument to control tab renderingrelease_trackattribute to PluginConfigOther Changes
modelattribute on PluginTemplateExtension (usemodelsinstead)ALLOW_TOKEN_RETRIEVALto Falsesqlmigratemanagement commandThis discussion was created from the release v4.3.0-beta1 - 2025-04-14.
Beta Was this translation helpful? Give feedback.
All reactions