Clarify migration actions and results in the UI

Abierto
  • ¿Algo no está bien?
#84 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
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
documentation, frontend

Línea de trabajo

Start by locating the migration pages and the relevant migration guide sections; the issue does not name their files or tests. Review how the listed migration actions and results are presented, then update the brief guidance and guide where needed. Done means users can understand the permission changes, readiness and next steps, Repoint’s scope, and the distinction between Verify’s report and Job completion.

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

Improve the brief guidance on the migration pages and link to the relevant sections of the migration guide:

  • Explain before inventory that Data Source Projects need a subdirectory, such as scripts/, and that scripts at the source root block staging.
  • Explain which Object Permissions cutover disables, including mixed permissions, which grants are transferred, and which need manual recreation.
  • Clarify revision statuses, Project readiness and the next steps.
  • Explain that Repoint references updates supported Event Rules, permissions and Job history, and recreates eligible captured runs. It does not move files in the source repository.
  • Display Verify’s report result separately from the Job’s completion status. Explain what it checks and that it does not run Scripts or verify stored source files.

Keep detailed explanations in the guide and update the relevant sections where needed.

Use case

Community testing raised questions about permission changes, Project readiness and how to interpret migration results.

The guide already covers much of this. Short explanations beside the relevant actions would help users understand what will change, what needs attention and what to do next.

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.