NetBox v3.2 support

[jeremystretch]

Hey there! I'd like to volunteer to implement support for NetBox v3.2. The first beta was recently released, and it greatly extends the plugins framework. We should be able to ensure support for NetBox v3.2 while removing a substantial amount of boilerplate/unsupported code. I did this recently for the netbox-dns plugin and it turned out very well.

If this would be helpful to you, I'll get to work shortly on a PR to adapt the current code base to the new framework. Of course it's entirely up to you whether to adopt the whole thing or implement specific changes piecemeal, but it should at least serve as a reference to hopefully minimize the work needed. Please let me know what you think!

[k01ek]

Hi @jeremystretch! Thank you very much for your attention to the NetBox plugin system and to this plugin in particular. And of course many thanks for your work on NetBox, it's a great project. I keep a close eye on the latest changes to the NetBox plugins framework. Unfortunately, I could not participate in discussion due to lack of free time, but everything I needed was already voiced there.
I saw the pull request you made for the dns plugin. I have already made a new plugin based on the 3.2 version. It's really easy to create and maintain plugins now. This is what I've been waiting for a long time.
As for the changes for this plugin, it would be great if you could contribute, but to be honest, I think you already have a lot of work.

[ryanmerolle]

I think there is huge value in @jeremystretch helping in that he will get better views on if the approach he took to introduce features or fixes from the plugin discussion truly helped or added any additional burden/complexity.

If @jeremystretch & @k01ek do not collaborate on this plugin update, I think a collaboration on k01ek/netbox-plugin-skeleton might be a good idea to lower the barrier for new plugin creators, set an example for existing maintainers (who many already use this template), and standardize the overall workflow of development.

[jeremystretch]

Like Ryan said, I benefit from this work too: Working through the migration process firsthand helps highlight tweaks that might still be needed to the plugins framework itself. We've already made a few resulting from the work I did on the DNS plugin. I think it'll really come into focus once I've gone through the same process with a few other plugins as well.

The plugin skeleton is also very cool! Interested to hear how you'd prefer to handle that for the new v3.2 framework.

[k01ek]

Okay, make the necessary changes. Let me know if you need any help or have questions.

[TheNetworkGuy]

Since Netbox 3.2 has been released, is it posible to update the plugin with a new tag for compatibility? :)

[k01ek]

@TheNetworkGuy sure! I am going to merge #85 and release new version this week.