starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Point out a possible cause of requiring migrations to be run is the addition of new plugins #9333

New Issue
Closed
opened 2025-12-29 20:48:38 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:48:38 +01:00
Owner
Copy Link

Originally created by @Supermathie on GitHub (Mar 7, 2024).

Change Type

Addition

Area

Development

Proposed Changes

If someone installs a plugin that has migrations of its own, they may not know to run migrations.

For example: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1709851212417359?thread_ts=1709848122.367389&cid=C01P0FRSXRV

Adding this case to the error message may help remind people to do so.

Originally created by @Supermathie on GitHub (Mar 7, 2024). ### Change Type Addition ### Area Development ### Proposed Changes If someone installs a plugin that has migrations of its own, they may not know to run migrations. For example: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1709851212417359?thread_ts=1709848122.367389&cid=C01P0FRSXRV Adding this case to the error message may help remind people to do so.
adam added the type: documentation label 2025-12-29 20:48:38 +01:00
adam closed this issue 2025-12-29 20:48:38 +01:00
adam commented 2025-12-29 20:48:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 8, 2024):

Migrations are only one part of installing a plugin. Each plugin is responsible for maintaining its own installation documentation, and the administrator performing the installation is obligated to follow it. It would not be feasible to prescribe sufficient installation instructions for every potential plugin in the NetBox documentation.

@jeremystretch commented on GitHub (Mar 8, 2024): Migrations are only one part of installing a plugin. Each plugin is responsible for maintaining its own installation documentation, and the administrator performing the installation is obligated to follow it. It would not be feasible to prescribe sufficient installation instructions for every potential plugin in the NetBox documentation.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9333
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?