Enhancement details
I would like to propose a new abstract class PoweredDevice with PhysicalDevice as a parent. This class would get a new field power_source_id which links to a PowerConnection.
The currently existing classes ConnectableCI, Enclosure, Rack and Peripheral would get this new class as their parent. This does not make much sense for mobile devices like tablets or phones.
This also provides a convenient extra powereddevices_list possibility on PowerConnection class to list all devices powered by this PDU/Source in a tab.
Automatic migration when upgrading is possible.
Are you willing to create (at a later stage) a PR for that?
Yes
iTop version
No response
Additional information (if needed)
It is not possible to do this with a custom extension as changing the parent of an existing class introduces cyclic dependency issues.
Enhancement details
I would like to propose a new abstract class
PoweredDevicewithPhysicalDeviceas a parent. This class would get a new fieldpower_source_idwhich links to aPowerConnection.The currently existing classes
ConnectableCI,Enclosure,RackandPeripheralwould get this new class as their parent. This does not make much sense for mobile devices like tablets or phones.This also provides a convenient extra
powereddevices_listpossibility onPowerConnectionclass to list all devices powered by this PDU/Source in a tab.Automatic migration when upgrading is possible.
Are you willing to create (at a later stage) a PR for that?
Yes
iTop version
No response
Additional information (if needed)
It is not possible to do this with a custom extension as changing the parent of an existing class introduces cyclic dependency issues.