FR: Include Associated Devices When Cloning Static Routes #113
Description
Plugin version
0.3.1
NetBox version
v4.4.4
Feature type
Change to existing functionality
Proposed functionality
Proposed functionality
When cloning a static route, any devices currently associated with that route are not included in the clone. As a result, users must manually reassign each device to the cloned route, which can be especially time-consuming when dealing with large sets of associated devices.
The proposed change is to include all existing device associations by default when cloning a static route. This ensures the cloned route is a complete duplicate of the original, including its device relationships.
Proposed behavior
When a user clones a static route, the new (cloned) static route should automatically inherit all device associations from the original route.
The rest of the static route’s attributes (e.g., prefix, description, VRF, etc.) should continue to be cloned as they currently are.
Benefits
Significantly reduces manual effort when cloning static routes linked to multiple devices.
Prevents potential data entry errors caused by reassigning devices manually.
Improves user experience by ensuring cloned static routes are functionally identical to their originals.
Streamlines configuration management and enhances consistency across network objects.
Use case
In environments where static routes are linked to numerous devices (for example, when managing large-scale, multi-device routing configurations), cloning an existing route currently requires reassigning each associated device manually.
This can involve dozens or even hundreds of device selections, leading to unnecessary administrative overhead and potential for manual error.
By automatically cloning the device associations, users can replicate complex routing configurations quickly and accurately, maintaining data integrity and consistency while significantly improving operational efficiency.
Benefits
- Reduces manual input and administrative time when duplicating static routes.
- Eliminates the risk of forgetting to reassign devices to cloned routes.
- Ensures cloned routes remain fully functional and consistent with their originals.
- Improves workflow efficiency for network engineers managing large deployments.
Database changes
No response
External dependencies
No response