Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NetBox plugins framework extensions #8333

Closed
13 tasks done
jeremystretch opened this issue Jan 12, 2022 · 1 comment
Closed
13 tasks done

NetBox plugins framework extensions #8333

jeremystretch opened this issue Jan 12, 2022 · 1 comment
Labels
status: accepted This issue has been accepted for implementation topic: plugins Relates to the plugins framework type: feature Introduction of new functionality to the application

Comments

@jeremystretch
Copy link
Member

jeremystretch commented Jan 12, 2022

NetBox version

v3.1.5

Feature type

New functionality

Proposed functionality

This issue is being opened to serve as a master tracker for the extension of the NetBox plugins framework. The introduction or expansion of individual components (TBD) will be listed as subtasks below. A working group is being formed to identify candidates.

Use case

Plugins were introduced in NetBox v2.8, but the original framework has not been extended significantly since then. This issue represents a formal initiative to extend the framework to better accommodate plugin developers, whose feedback and suggestions will influence the improvements being made.

Database changes

No response

External dependencies

No response

@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: under review Further discussion is needed to determine this issue's scope and/or implementation topic: plugins Relates to the plugins framework labels Jan 12, 2022
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Jan 21, 2022
This was referenced Apr 5, 2022
@jeremystretch
Copy link
Member Author

I'm going to close this out as its primary intent was to capture the expanded plugins framework in v3.2 as a single initiative. We will of course continue to expand on the plugins framework, but this iterative work can be tracked as regular feature requests moving forward.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation topic: plugins Relates to the plugins framework type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

1 participant