Support for subfolders in Reports/Scripts #3395

Closed
opened 2025-12-29 18:28:42 +01:00 by adam · 1 comment
Owner

Originally created by @mmahacek on GitHub (Feb 24, 2020).

Environment

  • Python version: 3.6
  • NetBox version: 2.7.7

Proposed Functionality

Support for detecting files in subfolders of Reports/Scripts

Use Case

The community repository has reports sorted into subfolders, and it could be helpful to users that want to just pull down the report repo structure as is, to more easily maintain changes to the files over time.

Database Changes

None

External Dependencies

None

Originally created by @mmahacek on GitHub (Feb 24, 2020). ### Environment * Python version: 3.6 * NetBox version: 2.7.7 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Support for detecting files in subfolders of Reports/Scripts <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case The community repository has reports sorted into subfolders, and it could be helpful to users that want to just pull down the report repo structure as is, to more easily maintain changes to the files over time. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 18:28:42 +01:00
Author
Owner

@jeremystretch commented on GitHub (Feb 24, 2020):

This would be a real pain to accommodate in the UI and API. It's also likely to frustrate future efforts around auto-detecting changes. I have to decline this one as the development burden it would introduce is disproportionate to the negligible benefit gained.

@jeremystretch commented on GitHub (Feb 24, 2020): This would be a real pain to accommodate in the UI and API. It's also likely to frustrate future efforts around auto-detecting changes. I have to decline this one as the development burden it would introduce is disproportionate to the negligible benefit gained.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3395