Replies: 1 comment 2 replies
|
I've converted this to the discussion as it does not include a detailed implementation proposal. Perhaps you can discuss with other community members to arrive at one and then we can revisit this as an actionable feature request. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
NetBox version
v4.5.4
Feature type
Change to existing functionality
Proposed functionality
Hello,
We are the creators of the plugin Netbox Docker Plugin and propose a change in the Netbox datamodel.
Users of the Netbox Docker Plugin reported that they wish to link their Docker > Container as a parent type of their IPAM > Application Service. So that when a user will create a new IPAM > Application Service he can choose a Parent Type "Docker > Container" like in the screenshot below:
So we will be able to connect the Netbox datamodel to the Docker Plugin Datamodel.
To address our users' request, we assessed the code of Netbox and found out that on the data-model level we can add a new parent_type of type Docker > Container. But the front-end, the view, is hard-coded to use only the 3 current options (see netbox/netbox/ipam/forms/model_forms.py at main · netbox-community/netbox · GitHub on line 320).
Could you please assess this feature and our request and let us know if you foresee any solution to add a Parent Type "Docker > Container" to a IPAM > Application Service?
Use case
Database changes
None
External dependencies
None
All reactions