dohertj2/ScadaBridge
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(claude): winrm re-enabled for deployment activities only (2026-09-28)

Browse Source 
The 2026-09-11 hold (WinRM exec tripped the wonder boxes' security software) is lifted for
deploys only: preflight, backup, stop/swap/start, migration, post-deploy verify, rollback.
Ad-hoc diagnostics and deployed-version checks use SMB/HTTP/SQL instead. psbridge stays retired.
This commit is contained in:
Joseph Doherty
2026-09-28 09:25:10 -04:00
parent fad833e8d1
commit fe89363b1a
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+8 -6
View File
@@ -26,12 +26,14 @@ Repos cloned as sibling directories under `~/Desktop/` — referenced for contex
Other peers in the `scadaproj` family (see `scadaproj/CLAUDE.md` for details): `~/Desktop/HistorianGateway` (`historiangw`) — AVEVA Historian gRPC sidecar, OtOpcUa's sole historian backend; its historian SDK (`AVEVA.Historian.Client`) is now owned inside that repo at `HistorianGateway/histsdk/` (the separate `~/Desktop/histsdk` repo was folded in with history); and `~/Desktop/scadaproj` (`scadaproj`) itself — shared `ZB.MOM.WW.*` libs + the dev/test GLAuth on `10.100.0.35:3893`. Other peers in the `scadaproj` family (see `scadaproj/CLAUDE.md` for details): `~/Desktop/HistorianGateway` (`historiangw`) — AVEVA Historian gRPC sidecar, OtOpcUa's sole historian backend; its historian SDK (`AVEVA.Historian.Client`) is now owned inside that repo at `HistorianGateway/histsdk/` (the separate `~/Desktop/histsdk` repo was folded in with history); and `~/Desktop/scadaproj` (`scadaproj`) itself — shared `ZB.MOM.WW.*` libs + the dev/test GLAuth on `10.100.0.35:3893`.
> ⛔ **Wonder box remote access (2026-09-11): no `psbridge`, no `winrm`.** Both skills are retired/disabled — > ⛔ **Wonder box remote access: `winrm` is DEPLOYMENT-ONLY (2026-09-28); `psbridge` stays retired.**
> the WinRM remote-exec channel set off the security software on the wonder boxes (vd03/vq03/vq04). Do not > WinRM remote exec set off the security software on the wonder boxes (vd03/vq03/vq04) and was
> run remote commands (service control, publish/swap, PowerShell) on those boxes and do not stand up a > disabled 2026-09-11; the user re-enabled the `winrm` skill on 2026-09-28 for deployment activities
> replacement channel until the user clears one. Still allowed: UNC/SMB file copies and logging directly > only (preflight, backup, stop/swap/start, migration, post-deploy verify, rollback of a deploy the
> into the SQL Servers. Deploy steps that need a command on the box are blocked; see the umbrella > user asked for). Ad-hoc diagnostics and "which version is deployed?" checks do NOT use WinRM —
> [`../scadaproj/CLAUDE.md`](../scadaproj/CLAUDE.md) for the current hold. > read the build stamp over SMB (a non-running `cli\*.dll`, or the `app.bak.<ts>` / `E:\psrem-stage`
> listings) and probe `/health/ready` over HTTP. UNC/SMB file copies and direct SQL logins are always
> allowed. See the skill's *Scope* section and the umbrella [`../scadaproj/CLAUDE.md`](../scadaproj/CLAUDE.md).
## Document Conventions ## Document Conventions