Show input parameters for queued and scheduled Script jobs

Open
  • Is something wrong?
#91 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
frontend

Research direction

Read issue #26 first, since it covers recording input summaries and their access and redaction rules. Then locate the Script run result page, Job detail page, and Script Jobs tab mentioned here, and check how they currently display queued runs. Done means users can review submitted inputs and recognizable object names on both pages, with an optional summary column distinguishing runs in the Jobs tab.

Written by the indexing model from the issue text.

Description

app: scripts complexity: low status: backlog type: feature
Plugin Version

v0.0.1

Proposed functionality

Display submitted input summaries on the Script run's result page and Job detail page, available as soon as the run is queued. Users should be able to review these values while a run is scheduled, pending or running.

Use recognizable names for selected objects, such as devices and sites. Add an optional summary column to the Script's Jobs tab so users can distinguish runs without opening each one.

This request covers UI presentation. Recording input summaries and defining their access and redaction rules are covered by #26.

Original request: netbox-community/netbox#23148.

Use case

When several runs of the same Script are queued for different devices or sites, the normal Job views do not show which target each run will use.
Showing the submitted inputs would help operators distinguish runs, confirm their intended targets before execution, and troubleshoot individual jobs without administrator access to the queue.

External dependencies

None expected.

Dominant language
Python
Stars
8
Forks
0
Avg merge
9h 34m
Merged PRs (30d)
32

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from netbox-community/netbox-scripts

All issues in netbox-community/netbox-scripts

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.