Clone a dashboard (built-in or customer) into a customer copy.

POST

/v1/projects/{projectId}/observability/dashboards/{dashboardId}/actions/clone

Code sample: Shell / cURL

curl --request POST \
  --url https://stratum.example.com/v1/projects/example/observability/dashboards/example/actions/clone \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "newName": "example" }'

• A Stratum cluster endpoint.

Authorizations

• bearerAuth

Parameters

Path Parameters

projectId

required

string

/^p-[a-z0-9-]+$/

dashboardId

required

string

/^db-[a-z0-9.-]+$/

Dashboard ID: db-… for a customer dashboard, db-builtin-<name> for a built-in one, and db-builtin-<name>-v<pack version> for a built-in published beside an operator edit.

Request Body

Media typeapplication/json

object

newName

Name for the clone. Defaults to <sourceName>-copy if omitted.

string

Example ^generated

{
  "newName": "example"
}

Responses

201

The cloned dashboard.

Media typeapplication/json

object

id

required

string

projectId

Empty for built-ins (cross-tenant).

string

name

required

string

displayName

required

string

description

string

body

required

dashboard document, rendered by stratum-ui, returned exactly as it was stored.

The control plane validates schemaVersion (must be 1), a top-level title, at least one widget, unique widgets[].id, a known widgets[].type, and datasource + query on data-fetching widgets. Everything else — description, tags, variables, layout, widgets[].position — is stored verbatim and not interpreted here. See CreateDashboardRequest.body for the full contract and a working example.

object

key

additional properties

any

origin

required

string

Allowed values: platform.builtin customer

state

required

string

Allowed values: active deleted

tags

object

key

additional properties

string

createdAt

required

string format: date-time

updatedAt

required

string format: date-time

deletedAt

string format: date-time

nullable

createdBy

required

string

Example

{
  "origin": "platform.builtin",
  "state": "active"
}

404

Resource not found.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}

409

Conflicting state.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}