netbox-dlm 0.1.0__tar.gz

netbox_dlm-0.1.0/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Blake Parker
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

netbox_dlm-0.1.0/PKG-INFO

@@ -0,0 +1,183 @@
+Metadata-Version: 2.4
+Name: netbox-dlm
+Version: 0.1.0
+Summary: Device/software/hardware lifecycle management plugin for NetBox
+Author-email: Blake Parker <blake.parker@e280.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/droolingtaz/netbox-dlm
+Project-URL: Issues, https://github.com/droolingtaz/netbox-dlm/issues
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: Django
+Classifier: Intended Audience :: System Administrators
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: System :: Networking
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: requests>=2.28
+Dynamic: license-file
+
+# netbox-dlm
+
+A NetBox plugin for hardware/software lifecycle management — built as a
+real NetBox plugin (Django models, not Custom Objects), since this needs
+background scripts, custom filtersets/API viewsets, and many-to-many
+scoping that Custom Objects doesn't support well.
+
+## What it models
+
+- `HardwareNotice` (DeviceType or ModuleType) — EoS/EoL/EoSecurity/EoSW dates
+- `SoftwareVersion` (per Platform)
+- `SoftwareImageFile`
+- `DeviceSoftware` — software actually running on a Device
+- `ValidatedSoftware` — approval rules
+- `Contract`
+- `Provider`
+- `CVE`
+- `Vulnerability`
+
+NetBox doesn't have native `SoftwareVersion`/`Contact` core models for
+this, so those are built from scratch here rather than reused.
+
+Reports are handled as **on-demand Scripts** (`scripts.py`) rather than
+stored "*Result" models — `CheckHardwareNotices` and `RunSoftwareValidation`
+compute compliance live against current data. This is a deliberate scope
+simplification; add stored result models later as ordinary `NetBoxModel`s
+if you want historical trending of compliance over time.
+
+## Package layout
+
+```
+netbox_dlm/
+├── __init__.py                          # PluginConfig
+├── models.py                            # Provider, Contract, HardwareNotice, SoftwareVersion,
+│                                        # SoftwareImageFile, DeviceSoftware, ValidatedSoftware,
+│                                        # CVE, Vulnerability
+├── choices.py                           # ChoiceSets
+├── admin.py                             # Django admin registrations
+├── forms.py                             # NetBoxModelForm / FilterSetForm classes
+├── tables.py                            # NetBoxTable classes
+├── filtersets.py                        # NetBoxModelFilterSet classes
+├── views.py                             # Generic CRUD views
+├── urls.py                              # UI URL routing
+├── navigation.py                        # Nav menu ("Device Lifecycle")
+├── template_content.py                  # Panels injected onto Device/DeviceType pages
+├── scripts.py                           # CheckHardwareNotices, RunSoftwareValidation, SyncCVEs
+├── templates/netbox_dlm/
+│   ├── device_lifecycle_panel.html
+│   └── devicetype_lifecycle_panel.html
+├── api/
+│   ├── serializers.py
+│   ├── views.py
+│   └── urls.py
+└── migrations/
+    └── __init__.py                       # run `manage.py makemigrations` in your env (see below)
+```
+
+## Installation
+
+1. Copy `netbox_dlm/` onto your NetBox host inside the same
+   Python environment as NetBox, or install it editable via the included
+   `pyproject.toml`:
+
+   ```bash
+   pip install -e /path/to/netbox_dlm
+   ```
+
+2. Add to `configuration.py`:
+
+   ```python
+   PLUGINS = [
+       "netbox_dlm",
+       # ... your other plugins
+   ]
+
+   PLUGINS_CONFIG = {
+       "netbox_dlm": {
+           "nist_api_key": None,       # optional, raises NVD API rate limits
+           "eos_warning_days": 180,
+       },
+   }
+   ```
+
+3. **Generate and apply migrations against your actual NetBox version** —
+   this repo intentionally ships without a pre-built migration, since exact
+   field/constraint behavior is sensitive to the NetBox version pinned in
+   your venv:
+
+   ```bash
+   cd /opt/netbox/netbox   # your NetBox root
+   python3 manage.py makemigrations netbox_dlm
+   python3 manage.py migrate
+   ```
+
+4. Restart NetBox (`systemctl restart netbox netbox-rq` or your equivalent).
+   You should see "Device Lifecycle" in the left nav, and Scripts under
+   Operations > Scripts grouped by this plugin.
+
+5. If you're serving static files separately behind a reverse proxy, run
+   `python manage.py collectstatic --no-input`.
+
+## Using it
+
+- **Providers / Contracts** — track who supports what, and which devices a
+  contract covers (`Contract.devices` M2M).
+- **Hardware Notices** — one row per `DeviceType` *or* `ModuleType` (not
+  both — enforced in `clean()`), with EoS/EoL/EoSecurity/EoSW dates.
+- **Software Versions / Images** — per `Platform`. `DeviceSoftware` is a
+  1:1 to `Device` recording what's actually running (populate this from your
+  existing sync tooling — e.g. alongside `aci_netbox_sync` runs, or a Golden
+  Config compliance pass).
+- **Validated Software** — approval rules scoped by `device_types`,
+  `device_roles`, and/or specific `devices` (M2M). A rule
+  with no scope at all applies to any device running that software version.
+  `preferred=True` marks the target version for a given scope; `covers_device()`
+  and `valid_now` do the compliance-check heavy lifting.
+- **CVE / Vulnerability** — `CVE.affected_software` M2M links a CVE to one or
+  more `SoftwareVersion`s; `Vulnerability` narrows that down to (optionally) a
+  specific `Device`, with its own `status` workflow (open → mitigated/resolved).
+- **Scripts** (Operations > Scripts > Device Lifecycle Management):
+  - `Check Hardware Notices` — flags past-due and upcoming EoS.
+  - `Run Software Validation` — flags devices whose recorded software has no
+    currently-valid `ValidatedSoftware` rule, or isn't the preferred version.
+  - `Sync CVEs from NIST NVD` — placeholder; wire up the actual NVD API 2.0
+    HTTP calls once your NetBox host has outbound access to
+    `services.nvd.nist.gov`.
+
+Device and DeviceType pages get a right-hand panel (via `template_content.py`)
+summarizing running software, compliance status, hardware notice, and open
+vulnerabilities at a glance.
+
+## Testing
+
+```bash
+./scripts/test-templates.sh
+```
+
+First run clones `netbox-community/netbox` (pinned to the version this
+plugin targets) and builds a venv under `.dev/` (gitignored, ~150MB);
+subsequent runs reuse it. It compiles every template in
+`netbox_dlm/templates/netbox_dlm/` through NetBox's real template engine —
+no database or Redis needed, since template compilation never touches the
+ORM. This catches `TemplateSyntaxError`/`TemplateDoesNotExist` (bad
+`{% load %}`, filters used where a tag was needed, missing includes)
+before they reach a deployed host. It won't catch bugs that only manifest
+at render time against real data (e.g. a table column referencing a model
+attribute that silently resolves to nothing) — there's no substitute for
+exercising the view against a real NetBox + Postgres instance for that.
+
+## What I didn't build (scope cuts, worth knowing about)
+
+- **Stored compliance-result models / history** — this plugin computes
+  compliance live via scripts rather than persisting result rows.
+  Straightforward to add later as another `NetBoxModel` if you want a
+  graphable history.
+- **Inventory item lifecycle** — hardware notices are scoped to
+  `Module`/`ModuleType` (NetBox's modern equivalent); if you're still
+  using NetBox's legacy `InventoryItem` model for non-modular gear, that's a
+  straightforward additional FK to add to `HardwareNotice`.
+- **VM software tracking** — `DeviceSoftware` only covers `Device`, not
+  `VirtualMachine`. Trivial to mirror if needed.
+- **Automated CVE ingestion** — `SyncCVEs` is a stub; NVD API 2.0
+  request/response handling needs to be written against whatever
+  auth/rate-limit setup you use.

netbox_dlm-0.1.0/README.md

@@ -0,0 +1,164 @@
+# netbox-dlm
+
+A NetBox plugin for hardware/software lifecycle management — built as a
+real NetBox plugin (Django models, not Custom Objects), since this needs
+background scripts, custom filtersets/API viewsets, and many-to-many
+scoping that Custom Objects doesn't support well.
+
+## What it models
+
+- `HardwareNotice` (DeviceType or ModuleType) — EoS/EoL/EoSecurity/EoSW dates
+- `SoftwareVersion` (per Platform)
+- `SoftwareImageFile`
+- `DeviceSoftware` — software actually running on a Device
+- `ValidatedSoftware` — approval rules
+- `Contract`
+- `Provider`
+- `CVE`
+- `Vulnerability`
+
+NetBox doesn't have native `SoftwareVersion`/`Contact` core models for
+this, so those are built from scratch here rather than reused.
+
+Reports are handled as **on-demand Scripts** (`scripts.py`) rather than
+stored "*Result" models — `CheckHardwareNotices` and `RunSoftwareValidation`
+compute compliance live against current data. This is a deliberate scope
+simplification; add stored result models later as ordinary `NetBoxModel`s
+if you want historical trending of compliance over time.
+
+## Package layout
+
+```
+netbox_dlm/
+├── __init__.py                          # PluginConfig
+├── models.py                            # Provider, Contract, HardwareNotice, SoftwareVersion,
+│                                        # SoftwareImageFile, DeviceSoftware, ValidatedSoftware,
+│                                        # CVE, Vulnerability
+├── choices.py                           # ChoiceSets
+├── admin.py                             # Django admin registrations
+├── forms.py                             # NetBoxModelForm / FilterSetForm classes
+├── tables.py                            # NetBoxTable classes
+├── filtersets.py                        # NetBoxModelFilterSet classes
+├── views.py                             # Generic CRUD views
+├── urls.py                              # UI URL routing
+├── navigation.py                        # Nav menu ("Device Lifecycle")
+├── template_content.py                  # Panels injected onto Device/DeviceType pages
+├── scripts.py                           # CheckHardwareNotices, RunSoftwareValidation, SyncCVEs
+├── templates/netbox_dlm/
+│   ├── device_lifecycle_panel.html
+│   └── devicetype_lifecycle_panel.html
+├── api/
+│   ├── serializers.py
+│   ├── views.py
+│   └── urls.py
+└── migrations/
+    └── __init__.py                       # run `manage.py makemigrations` in your env (see below)
+```
+
+## Installation
+
+1. Copy `netbox_dlm/` onto your NetBox host inside the same
+   Python environment as NetBox, or install it editable via the included
+   `pyproject.toml`:
+
+   ```bash
+   pip install -e /path/to/netbox_dlm
+   ```
+
+2. Add to `configuration.py`:
+
+   ```python
+   PLUGINS = [
+       "netbox_dlm",
+       # ... your other plugins
+   ]
+
+   PLUGINS_CONFIG = {
+       "netbox_dlm": {
+           "nist_api_key": None,       # optional, raises NVD API rate limits
+           "eos_warning_days": 180,
+       },
+   }
+   ```
+
+3. **Generate and apply migrations against your actual NetBox version** —
+   this repo intentionally ships without a pre-built migration, since exact
+   field/constraint behavior is sensitive to the NetBox version pinned in
+   your venv:
+
+   ```bash
+   cd /opt/netbox/netbox   # your NetBox root
+   python3 manage.py makemigrations netbox_dlm
+   python3 manage.py migrate
+   ```
+
+4. Restart NetBox (`systemctl restart netbox netbox-rq` or your equivalent).
+   You should see "Device Lifecycle" in the left nav, and Scripts under
+   Operations > Scripts grouped by this plugin.
+
+5. If you're serving static files separately behind a reverse proxy, run
+   `python manage.py collectstatic --no-input`.
+
+## Using it
+
+- **Providers / Contracts** — track who supports what, and which devices a
+  contract covers (`Contract.devices` M2M).
+- **Hardware Notices** — one row per `DeviceType` *or* `ModuleType` (not
+  both — enforced in `clean()`), with EoS/EoL/EoSecurity/EoSW dates.
+- **Software Versions / Images** — per `Platform`. `DeviceSoftware` is a
+  1:1 to `Device` recording what's actually running (populate this from your
+  existing sync tooling — e.g. alongside `aci_netbox_sync` runs, or a Golden
+  Config compliance pass).
+- **Validated Software** — approval rules scoped by `device_types`,
+  `device_roles`, and/or specific `devices` (M2M). A rule
+  with no scope at all applies to any device running that software version.
+  `preferred=True` marks the target version for a given scope; `covers_device()`
+  and `valid_now` do the compliance-check heavy lifting.
+- **CVE / Vulnerability** — `CVE.affected_software` M2M links a CVE to one or
+  more `SoftwareVersion`s; `Vulnerability` narrows that down to (optionally) a
+  specific `Device`, with its own `status` workflow (open → mitigated/resolved).
+- **Scripts** (Operations > Scripts > Device Lifecycle Management):
+  - `Check Hardware Notices` — flags past-due and upcoming EoS.
+  - `Run Software Validation` — flags devices whose recorded software has no
+    currently-valid `ValidatedSoftware` rule, or isn't the preferred version.
+  - `Sync CVEs from NIST NVD` — placeholder; wire up the actual NVD API 2.0
+    HTTP calls once your NetBox host has outbound access to
+    `services.nvd.nist.gov`.
+
+Device and DeviceType pages get a right-hand panel (via `template_content.py`)
+summarizing running software, compliance status, hardware notice, and open
+vulnerabilities at a glance.
+
+## Testing
+
+```bash
+./scripts/test-templates.sh
+```
+
+First run clones `netbox-community/netbox` (pinned to the version this
+plugin targets) and builds a venv under `.dev/` (gitignored, ~150MB);
+subsequent runs reuse it. It compiles every template in
+`netbox_dlm/templates/netbox_dlm/` through NetBox's real template engine —
+no database or Redis needed, since template compilation never touches the
+ORM. This catches `TemplateSyntaxError`/`TemplateDoesNotExist` (bad
+`{% load %}`, filters used where a tag was needed, missing includes)
+before they reach a deployed host. It won't catch bugs that only manifest
+at render time against real data (e.g. a table column referencing a model
+attribute that silently resolves to nothing) — there's no substitute for
+exercising the view against a real NetBox + Postgres instance for that.
+
+## What I didn't build (scope cuts, worth knowing about)
+
+- **Stored compliance-result models / history** — this plugin computes
+  compliance live via scripts rather than persisting result rows.
+  Straightforward to add later as another `NetBoxModel` if you want a
+  graphable history.
+- **Inventory item lifecycle** — hardware notices are scoped to
+  `Module`/`ModuleType` (NetBox's modern equivalent); if you're still
+  using NetBox's legacy `InventoryItem` model for non-modular gear, that's a
+  straightforward additional FK to add to `HardwareNotice`.
+- **VM software tracking** — `DeviceSoftware` only covers `Device`, not
+  `VirtualMachine`. Trivial to mirror if needed.
+- **Automated CVE ingestion** — `SyncCVEs` is a stub; NVD API 2.0
+  request/response handling needs to be written against whatever
+  auth/rate-limit setup you use.

netbox_dlm-0.1.0/netbox_dlm/__init__.py

@@ -0,0 +1,24 @@
+from netbox.plugins import PluginConfig
+
+
+class DeviceLifecycleConfig(PluginConfig):
+    name = "netbox_dlm"
+    verbose_name = "Device Lifecycle Management"
+    description = (
+        "Track hardware end-of-life/end-of-support notices, software versions and "
+        "validated-software compliance, CVE/vulnerability exposure, and maintenance "
+        "contracts — modeled after Nautobot's Device Lifecycle Management app."
+    )
+    version = "0.1.0"
+    base_url = "device-lifecycle"
+    min_version = "4.1.0"
+    default_settings = {
+        # Set to a NIST NVD API key to raise CVE-lookup rate limits (optional).
+        "nist_api_key": None,
+        # How many days out a hardware/software EoS date counts as "upcoming"
+        # for dashboard highlighting.
+        "eos_warning_days": 180,
+    }
+
+
+config = DeviceLifecycleConfig

netbox_dlm-0.1.0/netbox_dlm/admin.py

@@ -0,0 +1,72 @@
+from django.contrib import admin
+
+from .models import (
+    CVE,
+    Contract,
+    DeviceSoftware,
+    HardwareNotice,
+    Provider,
+    SoftwareImageFile,
+    SoftwareVersion,
+    ValidatedSoftware,
+    Vulnerability,
+)
+
+
+@admin.register(Provider)
+class ProviderAdmin(admin.ModelAdmin):
+    list_display = ("name", "phone", "email", "portal_url")
+    search_fields = ("name", "email")
+
+
+@admin.register(Contract)
+class ContractAdmin(admin.ModelAdmin):
+    list_display = ("name", "provider", "support_level", "start_date", "end_date")
+    list_filter = ("provider", "support_level")
+    search_fields = ("name", "contract_number")
+
+
+@admin.register(HardwareNotice)
+class HardwareNoticeAdmin(admin.ModelAdmin):
+    list_display = ("__str__", "end_of_sale", "end_of_support", "end_of_security_patches")
+    list_filter = ("end_of_support",)
+
+
+@admin.register(SoftwareVersion)
+class SoftwareVersionAdmin(admin.ModelAdmin):
+    list_display = ("__str__", "platform", "version", "release_date", "end_of_support", "long_term_support")
+    list_filter = ("platform", "long_term_support")
+    search_fields = ("version", "alias")
+
+
+@admin.register(SoftwareImageFile)
+class SoftwareImageFileAdmin(admin.ModelAdmin):
+    list_display = ("file_name", "software_version", "hashing_algorithm", "default_image")
+    list_filter = ("hashing_algorithm", "default_image")
+    search_fields = ("file_name", "checksum")
+
+
+@admin.register(DeviceSoftware)
+class DeviceSoftwareAdmin(admin.ModelAdmin):
+    list_display = ("device", "software_version", "last_checked")
+    search_fields = ("device__name",)
+
+
+@admin.register(ValidatedSoftware)
+class ValidatedSoftwareAdmin(admin.ModelAdmin):
+    list_display = ("software_version", "start", "end", "preferred", "valid_now")
+    list_filter = ("preferred",)
+
+
+@admin.register(CVE)
+class CVEAdmin(admin.ModelAdmin):
+    list_display = ("cve_id", "name", "severity", "status", "cvss_score", "published_date")
+    list_filter = ("severity", "status")
+    search_fields = ("cve_id", "name", "description")
+
+
+@admin.register(Vulnerability)
+class VulnerabilityAdmin(admin.ModelAdmin):
+    list_display = ("cve", "software_version", "device", "status")
+    list_filter = ("status",)
+    search_fields = ("cve__cve_id", "device__name")