HPC CONFIG UPDATE¶
Updates specific fields within an existing saved HPC configuration by accepting a flat JSON key-value object. Validates keys, enforces value constraints, and detects dependent field changes before persisting the result.
When to use¶
Tagged: config_update, hpc, hpc_config, job_submission, keyvalue, settings.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| HPC Setting | hpc_setting_id | remote_lookup | — | ✓ | Remote lookup reference to the existing saved HPC configuration record to be updated; select from the registered HPC settings list (remote_lookup_hpc_settings). |
| Key-Value Updates | keyvalue_updates | keyvalue | — | ✓ | Flat JSON key-value object specifying only the fields to change (e.g. {“queue”: “gpu”, “ncores”: 16}); keys not present here are left unchanged, invalid or constrained keys will be rejected and reported in the status message. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Updated HPC Config | updated_config | object | Complete HPC configuration JSON object reflecting all fields after the update has been applied; can be passed directly to job-submission workers. |
| Status Message | status_message | text | Human-readable text summarising which keys were successfully updated, which were rejected (with reasons), and any dependency or constraint warnings triggered by the changes. |
Disciplines¶
- platform.hpc_config
Auto-generated from platform schema. Worker id: hpc_config_update. Schema hash: 46c4e6d67903. Hand-curated docs in workerexamples/ override this page when present.