Creating a report or script from a remote data source does not retain the origin's directory hierarchy #7978

Closed
opened 2025-12-29 20:30:47 +01:00 by adam · 2 comments
Owner

Originally created by @jeremystretch on GitHub (May 2, 2023).

NetBox version

v3.5.0

Python version

3.8

Steps to Reproduce

  1. Create a git repository which stores a report and/or script within a subdirectory of the repo root.
  2. Create a remote data source in NetBox and synchronize the repo.
  3. Create a report or script from one of the files in the repo's subdirectory.

Expected Behavior

The report or script should be created within a local directory of the same name as the origin subdirectory.

Observed Behavior

The report or script is created within the corresponding root path locally, without replication the origin hierarchy.

Originally created by @jeremystretch on GitHub (May 2, 2023). ### NetBox version v3.5.0 ### Python version 3.8 ### Steps to Reproduce 1. Create a git repository which stores a report and/or script within a subdirectory of the repo root. 2. Create a remote data source in NetBox and synchronize the repo. 3. Create a report or script from one of the files in the repo's subdirectory. ### Expected Behavior The report or script should be created within a local directory of the same name as the origin subdirectory. ### Observed Behavior The report or script is created within the corresponding root path locally, without replication the origin hierarchy.
adam added the type: bugstatus: needs ownerpending closureseverity: medium labels 2025-12-29 20:30:48 +01:00
adam closed this issue 2025-12-29 20:30:48 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 25, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 25, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@jeremystretch commented on GitHub (Dec 26, 2023):

I'm going to close this out as an unsupported feature, given that it hasn't found any volunteers and there hasn't been much interest in the functionality.

@jeremystretch commented on GitHub (Dec 26, 2023): I'm going to close this out as an unsupported feature, given that it hasn't found any volunteers and there hasn't been much interest in the functionality.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7978