HPC SERVER UPDATE¶
Updates fields of an existing HPC server (admin-only) via a safe partial merge into the options blob (never a full replace). Rejects read-only/auto-managed fields and warns about disruptive changes (name change breaks routing-by-name; connection/scheduler/submit-time option changes).
When to use¶
Tagged: hpc, hpc_server, server, update, job_submission, admin.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| HPC Server Id | hpcserver_id | text | — | ✓ | Numeric id of the HPC server to update. |
| Key-Value Updates | keyvalue_updates | keyvalue | — | ✓ | Flat key-value object of fields to change (DB columns and/or options keys). Only listed keys change; read-only fields (supported_solvers/supported_queues/folder/id) are rejected and reported. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Updated HPC Server | updated_server | object | The HPC server record after the update. |
| Status Message | status_message | text | Summary of changed / rejected keys and any warnings (routing, scheduler, submit-time options). |
Disciplines¶
- platform.hpc_server
Auto-generated from platform schema. Worker id: hpc_server_update. Schema hash: 6ab84fba7dd9. Hand-curated docs in workerexamples/ override this page when present.