-
Notifications
You must be signed in to change notification settings - Fork 20
POC: Experimental support for upcoming NetBox v3.2 release #128
POC: Experimental support for upcoming NetBox v3.2 release #128
Conversation
thanks a lot for this! I hope I'll find the time to experiment with your code over the weekend and will provide some more detailed feedback as soon as I can manage. From looking at the code alone, the new interfaces look really promising and much cleaner than the former unsupported tweaks we used. You're correct in your observation that develop hasn't been updating lately, I think the maintainers should update the developer documentation accordingly (or change the process) - @hbasria, @hatsat32, any thoughts on this? |
Hi all! Sorry for the late response. Yes, we haven't been using the Thanks, @jeremystretch. Your changes look good. The new plugin framework looks really promising. I tested changes with the netbox feature branch and it worked really well with a few small changes. Here are the changes I did.
|
I think we can start implementing the new netbox plugin framework based on this PR. I created a new branch named Again thanks a lot. |
@peteeckel @hatsat32 thanks! I've pushed the changes mentioned above to bring this up to date with NetBox's current |
Thanks, @jeremystretch great job. Please give me a few days so that I can review the changes. |
@hatsat32 let me know if I can be of any help! |
CI/CD fails because the current test implementation uses netbox master branch but it is OK. |
Hi folks! As we approach the first beta release for NetBox v3.2, which introduces a greatly extended plugins API, I took a stab at updating this plugin to use the newly available resources. This PR is submitted as a proof of concept only and should not be treated as an actual proposed change at this time. (I based this PR off of the
main
branch as it appears thatdevelop
is no longer in use. Is that correct?)While this work has uncovered a few minor tweaks/extensions needed in the new plugins framework, I'm pretty happy with how smooth the implementation went overall. I've included a summary of the changes made thus far below. I would very much appreciate feedback: Did I miss anything? Is there something we could handle better? Do you foresee any issues with this approach? Let me know and we'll get it sorted. Thanks!
Summary
created
is now a DateTimeField on all change-logged modelsblank=True
attribute from tag managers (cosmetic change)tags
andobjects
attributes (now inherited from NetBoxModel), except where customextras_features()
(features are not provided by NetBoxModel)pk
fields (inherited from NetBoxModelBulkEditForm)Meta
classes and setmodel
on bulk edit formstags
filter declarations (inherited from NetBoxModelFilterSet)pk
column (inherited from NetBoxTable)configure_table()
utility withtable.configure()
object.html
withgeneric/object.html
object_list.html
withgeneric/object_list.html
record_list.html
andmanaged_record_list.html
withgeneric/object_list.html
action_buttons
on the viewspaginate_table()
withconfigure_table()
(not yet officially supported)