remove-model

What problem does it solve?

Removing a NetBox model cleanly is risky because many parts of the system (UI, APIs, GraphQL, tests, docs, navigation, and database migrations) may reference it, causing import or runtime failures.

Core Features & Use Cases

• End-to-end removal checklist: Guides you through deleting all consumers (tests, docs, nav, search, GraphQL, REST, URLs, views, tables, forms, filtersets, choices) before removing the model itself.
• Safety guardrails: Warns you to identify dependent models and non-nullable foreign keys first, so migrations and startup don’t break.
• Migration-first workflow: Directs you to generate the correct Django migration via makemigrations (including any RemoveField operations) and review it before applying.

Quick Start

Use the remove-model guide when you need to deprecate or delete an existing NetBox model after confirming nothing retained has non-nullable foreign keys pointing to it.