Add Container in Application Services

[lvenier]

4.X	1.X	1.X	1.X

Actual Behavior

In the netbox version 4.X services has been changed to application services.
When you want to create a new service you have 3 options possible :

Desired Behavior

I believe adding a 4rth option with the host and then selecting the container would have value for user who wants to expose services.

[strawhat-x]

We can manage to write a migration and create this parent type on the back-end, but unless we commit to netbox code source itself we can't force the interface to display it.

As the code below proves it:

/netbox/netbox/ipam/forms/model_forms.py from line 320:

   FieldSet(
            TabbedGroups(
                FieldSet('interface', name=_('Device')),
                FieldSet('vminterface', name=_('Virtual Machine')),
                FieldSet('fhrpgroup', name=_('FHRP Group')),
            ),
            'primary_for_parent', 'oob_for_parent', name=_('Assignment')

In addition, the infra-centric mindset of netbox suggests a split between the IPAM application services and the pure applicative layer.

Thats' why, I found interesting to propose a pure applicative layer mapped to the infrastructure in an "Application plugin" definition that you can find attached. Please let me know what you think of it :)

app-plugin-definition.txt
app-plugin-openapi.yaml