Build the read-only remote plan

Aperta
  • Qualcosa non va?
#86 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
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bash, powershell
Ambito
cli

Direzione di ricerca

Start on branch phase-5/remote-plan; read design 00 §5 and design 21 §5 and the existing plan command. Write bats and Pester acceptance tests first: unchanged hosts, skipped failed checks, returned logs. Done means remote plan --group runs over SSH and PowerShell remoting, returning plans without altering any host.

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

Descrizione

area: core platform: linux platform: windows type: build

Read first

Read these before starting. If this issue and the spec disagree, the spec wins; say so in the pull request.

Summary

Build remote plan <phase> --group <group>, a read-only way to see every host's plan from one place. Remote mode runs from a control node, a hardened server that can reach every host over SSH (Linux) or PowerShell remoting (Windows). A plan is the list of changes a run would make, with nothing changed. Today a person must log in to each host to see its plan; this is built first and remote apply (#87) waits until it has run safely in the lab.

Depends on

  • Blocked by #66 (automatic runs and the approval queue) and #65 (the command line and the installed laby).
  • Blocks #87 (remote apply).

Location & Context

  • Branch: phase-5/remote-plan. Specs: design 00, section 5 and design 21, section 5.
  • A new remote command in both runners (labyrinth.sh, labyrinth.ps1), run on the control node. Record its name and options in Conventions 3.3 first, then add it to the manual and docs/Commands.md.
  • Tests: new bats and Pester files, and tests/manual/manual.bats. The lab pass uses the control node and several hosts (docs/lab/README.md).

Current Behavior

A person must log in to every host to see its plan. Without remote plan, no view of all hosts exists from one control node.

Plan

  1. Build remote plan <phase> --group <group> over SSH and PowerShell remoting.
  2. Copy and check the release on each host (design 21, sections 5 and 5.1), run the local plan, and bring back the plans and logs.
  3. Change nothing on the hosts.

Acceptance tests

Write these first, in bats and Pester:

  • remote plan leaves every host unchanged (inventory identical before and after).
  • A host whose release check fails is not run.
  • Plans and logs come back for every host in the group.
  • Negative test: protected accounts and scored services are untouched before and after.

Done when

  • The Linux and Windows versions both pass CI.
  • The tests above pass in the lab on a control node and hosts of both platforms (docs/lab/README.md), before #87 starts.
  • The command is in both runners, the manual, docs/Commands.md, its -h page, the Conventions table and both test suites, in one branch (Roadmap section 2). Help never runs anything.

Out of scope

  • Making changes on hosts: remote apply, #87.
  • The signature check on the control node, and cleanup: #105.
  • Scheduled probes and checkpoints from the control node: #91.
  • Getting the release onto a host when there is no control node: #71.
Lingua principale
PowerShell
Stelle
0
Fork
0
Merge medio
2h 7m
PR unite (30g)
53

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 dotnetdork/Labyrinth

Tutte le issue di dotnetdork/Labyrinth

Issue simili

Altre issue su CLI

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.