Clarify migration actions and results in the UI

Aperta
  • Qualcosa non va?
#84 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
documentation, frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

app: scripts Bucket: Improve 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.

Lingua principale
Python
Stelle
8
Fork
0
Merge medio
11h 41m
PR unite (30g)
38

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di netbox-community/netbox-scripts

Tutte le issue di netbox-community/netbox-scripts

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.