Plugin Candidates #8364
Replies: 1 comment 1 reply
-
I'm just one person, but I think some sort of Change Management plugin (for stuff that can't be automated, or things like physical maintenance/etc) could be useful as well. I'm looking to try to leverage the Journal Entries to handle it - an Info entry using markdown to link back to a MOP/SOP for the change in Google Docs, and using GDocs "approval" to insure that the MOP is vetted by the appropriate people before it gets executed. Then another Info entry can indicate start of work, and a final Journal Entry can indicate Success or Warning/Critical for a failed MOP. But I have to imagine it could be done more elegantly with a plugin somehow (then approvals could be tracked in the DB, the MOPs themselves can be DB items, etc). |
Beta Was this translation helpful? Give feedback.
-
As an FYI, if you ever wanted to see feature requests that were tagged as good plugin candidates check this out plugin candidate for just that.
After watching issues, slack google groups, reddit, and etc, I have found some interesting/popular plugin ideas mentioned over the years:
As a reminder if an FR/issue gets suggested for a plugin candidate its often because the idea is either outside of the core functionality of NetBox, thought to be needlessly complex if added to core NetBox, or just not worth the ROI to implement or maintain. Plugins functions could be pulled into NetBox core if popular and if the plugin approach was well put together. Example would be social auth inclusion in NetBox in place of need to role you own SSO plugin.
You can find a number of interesting existing NetBox Plugins at the NetBox Plugin Topic page in GitHub .. (Be advised some projects tagged as NetBox Plugins are not, and GitHub does not restrict users from applying said topic to their project.)
Beta Was this translation helpful? Give feedback.
All reactions