admin343/browser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: expose server deployment trigger

Browse Source
This commit is contained in:
npc0-hue
2026-07-28 15:11:01 +08:00
parent e4ef4024a8
commit c5806cc6b7
10 changed files with 151 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/fix-server-deployment-trigger/proposal.md
+24
View File
@@ -0,0 +1,24 @@
## Why
The dedicated SCUM Run can register successfully, but a failed or draft server has no visible Platform action that submits its existing deployment definition. Operators therefore see an idle Run startup log and cannot advance the installation workflow.
## What Changes
- Add an explicit Deploy / Retry deploy control to the server detail actions for draft and failed servers.
- Submit the existing protected deployment definition through the existing authenticated deployment API, using the current config version and a fresh idempotency key.
- Present the queued deployment result in the normal operation feedback and refresh the server/job view.
## Capabilities
### New Capabilities
- `server-deployment-trigger`: Operator-facing dispatch of an already-configured draft or failed server deployment after its dedicated Run registers.
### Modified Capabilities
- None.
## Impact
- Affects `platform_web/pages/ServerDetailPage.tsx` and its focused UI tests.
- Reuses the existing `POST /api/v1/server-instances/{id}/deploy` contract; no new server API, remote access, credentials, or host data are introduced.