import#

dpsctl topology import Usage Guide#

Import a datacenter topology from a JSON file. The file must match the published topology schema. Refer to Import a Topology for the full workflow and an example file.

Import creates missing entities and then creates the named topology. The created topology is inactive. There is no single import RPC; the CLI orchestrates ListTopologies, GetEntities, CreateEntities, and CreateUpdateTopology.

Usage#

dpsctl topology import <filename>

Flags#

Includes global dpsctl options.

   --help, -h        show help

Examples#

Basic Usage#

$ dpsctl topology import topology.json
{
  "status": {
    "ok": true,
    "diag_msg": "Success"
  }
}

Notes#

  • A topology JSON filename is required.

  • The file must include a Topology object with at least one entity.

  • A nonempty top-level Policies array is rejected by the DPS 0.9 Go CLI before the import request is sent. Create typed policy bundles with dpsctl policy bundle upsert.

  • The topology JSON cannot carry a bundle selection. Import resolves the current global_policy_bundle setting and persists it on the new topology. Set that setting to the intended bundle before import; importing the same file under a different default selects a different bundle.

  • Import does not activate the topology or apply BMC power policies.

  • If the topology name already exists, import fails before entity creation.

  • If entity creation succeeds and topology creation fails, the new entities remain.