update
dpsctl topology update Usage Guide
Update an existing topology from a JSON file.
Usage
dpsctl topology update <filename>Flags
Includes global dpsctl options.
--force force update topology
--help, -h show helpExamples
Basic Update
$ dpsctl topology update updated-topology.json
{
"status": {
"ok": true,
"diag_msg": "Topology updated successfully"
}
}Force Update
$ dpsctl topology update topology.json --force
{
"status": {
"ok": true,
"diag_msg": "Topology forcefully updated"
}
}Update with Validation Errors
$ dpsctl topology update invalid-topology.json
{
"status": {
"ok": false,
"diag_msg": "Topology update failed: validation errors found"
}
}Notes
- A topology JSON filename is required.
- Non-forced updates require the input file to include
topologyHashfor the existing topology. - Updates modify existing topology configuration
- The
--forceflag bypasses the missingtopologyHashclient-side check. The topology model is still validated before it is applied. - Topology must be deactivated before major structural changes
- Use with caution as updates can affect active resource groups
- Always validate the JSON file with
dpsctl topology validatefirst