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

Create a plugin migration guide for NetBox v4.0 #15043

Closed
jeremystretch opened this issue Feb 5, 2024 · 1 comment
Closed

Create a plugin migration guide for NetBox v4.0 #15043

jeremystretch opened this issue Feb 5, 2024 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: documentation A change or addition to the documentation
Milestone

Comments

@jeremystretch
Copy link
Member

Change Type

Addition

Area

Plugins

Proposed Changes

Add a migration guide to the plugin development documentation detailing relevant changes in NetBox v4.0 for plugin maintainers. Example topics include:

  • Any breaking changes to the plugins API
  • Relocation/removal of internal components
  • HTML template changes
  • UI design changes
@jeremystretch jeremystretch added type: documentation A change or addition to the documentation status: accepted This issue has been accepted for implementation labels Feb 5, 2024
@jeremystretch jeremystretch added this to the v4.0 milestone Feb 5, 2024
@peteeckel
Copy link
Contributor

Some input from the migration of NetBox DNS to 4.0:

peteeckel/netbox-plugin-dns#153

This PR will be updated over time, following the development of the NetBox feature branch.

@jeremystretch jeremystretch self-assigned this Mar 19, 2024
jeremystretch added a commit that referenced this issue Apr 1, 2024
* Add v4.0 migration guide for plugins

* Note Python 3.12 support

* 15403 update GraphQL plugin conversion docs

* Add section on FieldSets

---------

Co-authored-by: Arthur <worldnomad@gmail.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 1, 2024
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 type: documentation A change or addition to the documentation
Projects
None yet
Development

No branches or pull requests

2 participants