You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
NetBox 3.1.0 added the new ASN model allowing you to specify multiple sites to an ASN. It would be ideal to leverage said model, and extend it in the same way you have within this BGP plugin.
Describe the solution you'd like
Deprecate the custom plugin model for ASNs and leverage the core NetBox model. The only difference between the two is that the core model allows for:
multiple sites per ASN
tenant group assignments for ASNs
An RIR association
IE that means no current attribute of the netbox-plugin model would be missing.
Sessions would just be linked to the NetBox core model of ASN.
Describe alternatives you've considered
Keep the two separate and continue confusion within the API and UI.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
There's also a conflict between the native ASNTable and the plugins' ASNTable interface configuration settings.
The thing is that a native one has the 'asn' field that is representing the number of AS, while the plugin has the 'number' field for that purpose. Each time I'm changing the table display setting for each table it rewrites the settings for another one.
Hi @k01ek first of all cool work!
Im currently thinking on using your plugin too but i was wondering if i should wait till this change is implemented. Do you have any eta?
Is your feature request related to a problem? Please describe.
NetBox 3.1.0 added the new ASN model allowing you to specify multiple sites to an ASN. It would be ideal to leverage said model, and extend it in the same way you have within this BGP plugin.
Describe the solution you'd like
Deprecate the custom plugin model for ASNs and leverage the core NetBox model. The only difference between the two is that the core model allows for:
IE that means no current attribute of the netbox-plugin model would be missing.
Sessions would just be linked to the NetBox core model of ASN.
Describe alternatives you've considered
Keep the two separate and continue confusion within the API and UI.
Additional context
N/A
The text was updated successfully, but these errors were encountered: