You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable a toggle per device role that allows a device (physical/vm) to be checked for uniqueness upon creation of a new item.
Use Case
As per the implementation of #2669 in 2.71, device names were made non unique.
This enables generic device types (patch panels, cables), however it allows the possibility of introducing a conflict in the database for a unique device (eg logical router).
Whilst this can be addressed re-actively by validation (reports) for users that use Netbox as their network source of truth this problem can be magnified by automation that is in place and increase the difficulty of cross system API calls that use the Device name as an identifier.
Database Changes
None
External Dependencies
None
The text was updated successfully, but these errors were encountered:
however it allows the possibility of introducing a conflict in the database for a unique device (eg logical router).
This is not a conflict, but a violation of your particular organization's naming/provisioning policy. If you need to restrict certain device roles to have no more than n instances, it will need to be done using a custom script or other custom mechanism. NetBox does not support conditional uniqueness enforcement for any models and we have no plans to introduce it at this time.
Environment
Proposed Functionality
Enable a toggle per device role that allows a device (physical/vm) to be checked for uniqueness upon creation of a new item.
Use Case
As per the implementation of #2669 in 2.71, device names were made non unique.
This enables generic device types (patch panels, cables), however it allows the possibility of introducing a conflict in the database for a unique device (eg logical router).
Whilst this can be addressed re-actively by validation (reports) for users that use Netbox as their network source of truth this problem can be magnified by automation that is in place and increase the difficulty of cross system API calls that use the Device name as an identifier.
Database Changes
None
External Dependencies
None
The text was updated successfully, but these errors were encountered: