Plan device actions exclusively as approved scripts and provide reboot library revisions
This commit is contained in:
+17
-6
@@ -1,4 +1,4 @@
|
||||
# Linux-MVP WebUI
|
||||
# Rust Discovery WebUI
|
||||
|
||||
React/TypeScript, no runtime demo data, no desktop/PTY/hypervisor integration.
|
||||
Build assets: **`web/dist/`**; serve `index.html` and `/assets/*` from the TLS backend
|
||||
@@ -6,16 +6,27 @@ on the same origin. Do not proxy authentication to a different origin. All API U
|
||||
are relative; cookies use `credentials: same-origin`, mutations use `X-CSRF-Token`.
|
||||
No token or password persistence, raw HTML rendering, automatic approval or retry.
|
||||
|
||||
## Geräteaufträge
|
||||
|
||||
Unter **Aufträge → Neuer Auftrag** wählen Sie die Geräte und eine veröffentlichte
|
||||
Skriptversion oder geben ein einmaliges Skript ein. **Neustartskript auswählen**
|
||||
übernimmt die passende Bibliotheksversion für Windows (PowerShell als SYSTEM) oder
|
||||
Linux (Shell als root). Gebundene Skriptbytes, Zielgeräte, Rechte und Zeitgrenzen
|
||||
sind vor der Entscheidung unter **Genehmigungen** sichtbar. Frühere typisierte
|
||||
Aufträge bleiben in der Historie lesbar. Im Gerätedetail stehen die zuletzt vom
|
||||
Agenten gemeldeten Ausführungsrechte. `full_maintenance_v1` bezeichnet das
|
||||
technische Profil eines genehmigten Administratorskripts.
|
||||
|
||||
## Commands
|
||||
|
||||
From `web/`: `npm ci`, `npm run typecheck`, `npm test`, `npm run build`.
|
||||
`npm run dev` binds loopback, but is not the authenticated TLS acceptance setup.
|
||||
The current server is `discovery.ease-technologies.de`; management access uses the
|
||||
configured SSH tunnel and verified TLS. Earlier local `rmm-dev.internal:18443`
|
||||
The public management service is documented in [public access](../docs/public-access.md).
|
||||
The separate dev/test profile uses the SSH tunnel. Earlier local `rmm-dev.internal:18443`
|
||||
examples below are historical. The notebook is development only, without an RMM
|
||||
server or enrolled agent. No certificate-verification bypass is supported.
|
||||
|
||||
## Script console (specification 1.20, source implementation)
|
||||
## Historical script console and adapter contracts (specification 1.20)
|
||||
|
||||
`run_script` remains a durable plan/request, not a PTY or interactive terminal.
|
||||
The planner accepts complete fixed POSIX/Bash or Windows PowerShell5.1 scripts.
|
||||
@@ -69,7 +80,7 @@ independent scopes. Two output tests cover hostile HTML/terminal/bidi bytes,
|
||||
unknown/cancellation/truncation, invalid encodings and absent/invalid results.
|
||||
No browser, server, VM job, approval or deployment was executed in these checks.
|
||||
|
||||
## JSON adapter contract
|
||||
### JSON adapter contract at the time of the historical tests
|
||||
|
||||
`src/api.ts` is the sole transport/contract boundary. Responses missing required
|
||||
fields fail explicitly. Unknown backend fields are displayed without interpretation.
|
||||
@@ -153,7 +164,7 @@ visible; failed polling retains the old response alongside an error, never a gre
|
||||
success message. Tenant changes unmount all selection/plans/jobs and abort requests.
|
||||
List pagination uses server cursors, without pretending a truncated page is complete.
|
||||
|
||||
## Browser checks and separate acceptance gates
|
||||
### Historical browser checks and separate acceptance gates
|
||||
|
||||
`tests/browser/approval.spec.ts` uses actual UI interactions only. It never uses an
|
||||
API client to authorize, never writes storageState, and disables traces/screenshots/
|
||||
|
||||
Reference in New Issue
Block a user