View revision source files in the UI
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 62/100
Research direction
Start at the revision's Files view and trace how it identifies active and retained revisions and reads from the verified revision store. Check the view permission and source-display behavior for text, binary, and oversized files; done when the selected revision is explicit, content is escaped and size-limited, and Script-run permission alone is insufficient.
Written by the indexing model from the issue text.
Description
Plugin Version
v0.0.1
Proposed functionality
Add a read-only source page for text files listed in a revision's Files view. Identify the selected revision clearly and support both active and retained historical source.
Read from the verified revision store without importing the module. Require netbox_scripts.view_scriptprojectrevision and the corresponding object access; permission to run a Script should not grant source access on its own.
Escape displayed content, apply a documented size limit, and explain when a binary or oversized file cannot be displayed. Editing is outside this request.
Use case
Operators need to inspect what a Script will do and review the exact source associated with an earlier run. The current Files view shows metadata but not file contents.
External dependencies
No new package or service is expected. Syntax highlighting is optional.
- Dominant language
- Python
- Stars
- 8
- Forks
- 0
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 32
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
-
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
-
Failed REST uploads expose internal error detailsPossibly taken @pheus claimed this 2 days ago. 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
-
app: scripts severity: low status: backlog type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netbox-community/netbox-scripts#74 ·
Maintainers usually reply within 1 day
-
Correct the release checklist's tag and publishing stepsPossibly taken @pheus claimed this 7 days ago. Openapp: scripts status: accepted type: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
netbox-community/netbox-scripts#68 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in netbox-community/netbox-scripts
Similar issues
-
fuzz fuzz-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
neilsh/stunt-reel#220 ·
Maintainers usually reply within 1 day
-
[Issue]: use_fp4_cache is accepted but ignored; the launcher always writes FP8 recordsPossibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area: cli priority: p3 size: S type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
finos/open-resource-broker#757 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days