Is your feature request related to a problem? Please describe.
Currently the subnet module can handle nested subnets via the parent parameter. As phpIPAM handles subnets and folders in the same namespace we need to refactor our subnet module.
Describe the solution you'd like
We propose to manage either parent or folder in separate parameters in subnet module. These parameters needs to be mutual exclusive. This way we have the chance to use the current phpipam_helper.py methods to resolve given names/cidrs to an id.
Describe alternatives you've considered
Another solution could be the recycling of the existing parent parameter to use for either a containing subnet or folder. This solution needs more efford to be implemented as we need to cover all possible issues related to wrong user inputs.
Additional context
No matter which solution will be implemented the parameter is_folder needs to be removed from subnet module as folders will be managed by its own module.
Is your feature request related to a problem? Please describe.
Currently the
subnetmodule can handle nested subnets via theparentparameter. As phpIPAM handles subnets and folders in the same namespace we need to refactor our subnet module.Describe the solution you'd like
We propose to manage either parent or folder in separate parameters in
subnetmodule. These parameters needs to be mutual exclusive. This way we have the chance to use the currentphpipam_helper.pymethods to resolve given names/cidrs to an id.Describe alternatives you've considered
Another solution could be the recycling of the existing
parentparameter to use for either a containing subnet or folder. This solution needs more efford to be implemented as we need to cover all possible issues related to wrong user inputs.Additional context
No matter which solution will be implemented the parameter
is_folderneeds to be removed fromsubnetmodule as folders will be managed by its own module.