Record a privacy-aware summary of run inputs

Abierto
  • ¿Algo no está bien?
#26 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, security

Línea de trabajo

Begin by mapping the queueing path, recurring successors, and NetBox Job access boundary described in the issue. Define the recording and access policy before implementation, covering sensitive variables, model references, uploads, Event Rule snapshots, revisions, and omissions. Done means permitted JSON-safe summaries are retained without credentials or file contents and redactions are identified without exposing values.

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

Descripción

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

v0.0.1

Proposed functionality

Save a JSON-safe summary of each run's inputs alongside its execution provenance, so the history remains useful after its queue task is gone.

Define the recording and access policy first. Cover sensitive variables, model references, uploads, and Event Rule snapshots, including who can read data stored on a NetBox Job. Do not store credentials or file contents by default. Identify omitted or redacted fields without exposing their values.

Capture the permitted summary when queueing the run, carry it to recurring successors, and record the revision actually used by each occurrence. Replaying historical inputs remains separate work.

Use case

Investigating a run requires knowing both which code executed and what it was asked to do. Operators need that context, while authors need clear rules about which inputs are retained and who can see them.

External dependencies

No new package or service is expected.

Lenguaje dominante
Python
Estrellas
8
Forks
0
Merge medio
11 h 22 min
PR fusionados (30 d)
40

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.