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

Add support for sub-packaging of reports #1529

New Issue
Closed
opened 2025-12-29 16:32:43 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:32:43 +01:00
Owner
Copy Link

Originally created by @dougthor42 on GitHub (Feb 2, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.8

Description

Reports are amazing. Since they're basically just Python packages, it makes sense that a user should be able to make an arbitrary number of sub-packages in the reports directory.

netbox/reports/
├───__init__py
├───assets.py
├───addresses.py
├───checks/
│   ├───__init__.py
│   ├───check_serials.py
└───inventory/
    ├───__init__.py
    ├───list_inventory.py
    └───list_ipv6.py

Reports above could be called via:

POST /api/extras/reports/checks.check_serials.CheckSerials/run/
Originally created by @dougthor42 on GitHub (Feb 2, 2018). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: 2.2.8 ### Description Reports are amazing. Since they're basically just Python packages, it makes sense that a user should be able to make an arbitrary number of sub-packages in the `reports` directory. ``` netbox/reports/ ├───__init__py ├───assets.py ├───addresses.py ├───checks/ │ ├───__init__.py │ ├───check_serials.py └───inventory/ ├───__init__.py ├───list_inventory.py └───list_ipv6.py ``` Reports above could be called via: ``` POST /api/extras/reports/checks.check_serials.CheckSerials/run/ ```
adam closed this issue 2025-12-29 16:32:43 +01:00
adam commented 2025-12-29 16:32:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

Each report is already a collection of related tests. I don't see the need to further group reports into directories, and fear doing so would complicate the UI.

@jeremystretch commented on GitHub (Jul 18, 2018): Each report is already a collection of related tests. I don't see the need to further group reports into directories, and fear doing so would complicate the UI.
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
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#1529
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?