Show input parameters for queued and scheduled Script jobs

Abierto
  • ¿Algo no está bien?
#91 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
8
Forks
0
Merge medio
9 h 34 min
PR fusionados (30 d)
32

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de netbox-community/netbox-scripts

Todos los issues de netbox-community/netbox-scripts

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.