Allow a Script Project to use a Data Source root
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
Research direction
Start by tracing the model validation, database constraints, and migration-planning paths mentioned in the issue. Define behavior for an empty data_path, exclusion of other Projects, documentation and CI-triggered revisions, and migration grouping when root and subdirectory scripts coexist; done means these cases are consistently specified and covered.
Written by the indexing model from the issue text.
Description
Plugin Version
v0.0.1
Proposed functionality
Let an empty data_path select the root of a Data Source rather than requiring a wrapper directory.
A root Project must exclude all other Projects on that Data Source, including a second root Project. Apply this consistently in model validation, database constraints, and migration planning.
Document that normal ingestion rules still apply: changes to documentation or CI files can also create revisions. Define migration grouping when root-level scripts and scripts in subdirectories coexist.
Use case
A repository dedicated to one Script Project should be usable directly. Subdirectory Projects would remain available for repositories containing unrelated content.
External dependencies
No new package or service is expected.
- Dominant language
- Python
- Stars
- 8
- Forks
- 0
- Avg merge
- 9h 56m
- Merged PRs (30d)
- 29
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from netbox-community/netbox-scripts
-
Run links keep only the last value of repeated query parametersPossibly taken @pheus claimed this today. Openapp: scripts severity: medium status: accepted type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
netbox-community/netbox-scripts#83 · 1 assignee ·
Maintainers usually reply within 1 day
-
app: scripts status: backlog type: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
netbox-community/netbox-scripts#80 ·
Maintainers usually reply within 1 day
-
Cleanup confirmation treats retained Job history as a blockerPossibly taken @pheus claimed this today. Openapp: scripts severity: medium status: accepted type: bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
netbox-community/netbox-scripts#79 · 1 assignee ·
Maintainers usually reply within 1 day
-
Failed REST uploads expose internal error detailsPossibly taken @pheus claimed this today. Openapp: scripts severity: medium status: accepted type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
netbox-community/netbox-scripts#77 · 1 assignee ·
Maintainers usually reply within 1 day
-
app: scripts severity: low status: backlog type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
netbox-community/netbox-scripts#76 ·
Maintainers usually reply within 1 day
All issues in netbox-community/netbox-scripts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/onnxscript#3155 ·
Maintainers usually reply within 4 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug docs severity:low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100