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 help

Examples#

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 topologyHash for the existing topology.

  • The topology must be inactive before it can be updated.

  • This Go command omits the policy-bundle field, so it preserves the current topology selection. An API client can explicitly update the optional policy_bundle field while the topology is inactive.

  • The --force flag bypasses the missing topologyHash client-side check. The topology model is still validated before it is applied.

  • Always validate the JSON file with dpsctl topology validate first