Set what a cluster is called and what it is for (browser session)

Sets the environment label and, when the body carries one, the criticality that decides how loudly the cluster reports. Both are written in a single transaction because to the operator they are one decision: picking an environment without a matching criticality is how a cluster ends up labelled for testing while the insight scanner still grades every finding on it at production weight. A body without a criticality leaves the stored one untouched and answers with the environment alone, which is the shape every caller written before the two settings were merged sends and expects. Requires clusters.write.

PATCH /org/clusters/imported/{cluster_id}/environment

Set what a cluster is called and what it is for (browser session)

Python

import requests

url = "https://api.platform.ankra.app/org/clusters/imported/{cluster_id}/environment"

payload = { "environment": "<string>" }
headers = {
    "cookie": "ankra_session=",
    "Content-Type": "application/json"
}

response = requests.patch(url, json=payload, headers=headers)

print(response.text)

200

{
  "criticality": "production",
  "environment": "<string>"
}

Authorizations

ankra_session · string · cookie · required

Browser session. Mutations also require X-Ankra-CSRF.

Path Parameters

cluster_id · string<uuid> · required

Body

application/json

environment · string · required

Required string length: 1 - 50

criticality · enum<string>

Available options: production, staging, development, disposable

Response

200

application/json

The stored environment, and the stored criticality when the request set one

criticality · enum<string>

Available options: production, staging, development, disposable

environment · string