import requests
url = "https://platform.ankra.app/api/v1/org/ci-settings/pool/{cluster_id}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text)const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/api/v1/org/ci-settings/pool/{cluster_id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request DELETE \
--url https://platform.ankra.app/api/v1/org/ci-settings/pool/{cluster_id} \
--header 'Authorization: Bearer <token>'{
"is_pooled": true,
"members": [
{
"cluster_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"cluster_name": "<string>",
"weight": 500,
"is_primary": true,
"is_listed": true,
"created_at": "2023-11-07T05:31:56Z"
}
]
}Remove a CI pool member
Unlists one cluster from the organisation’s CI pool and answers the pool that remains. Runs already pinned to it finish there. Unlisting the declared ci_cluster_id removes only its weight: it stays the implicit primary member. Organisation admins only. A browser session twin is mounted at the same path without the /api/v1 prefix (cookie authentication; writes also need the X-Ankra-CSRF header).
import requests
url = "https://platform.ankra.app/api/v1/org/ci-settings/pool/{cluster_id}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text)const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/api/v1/org/ci-settings/pool/{cluster_id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request DELETE \
--url https://platform.ankra.app/api/v1/org/ci-settings/pool/{cluster_id} \
--header 'Authorization: Bearer <token>'{
"is_pooled": true,
"members": [
{
"cluster_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"cluster_name": "<string>",
"weight": 500,
"is_primary": true,
"is_listed": true,
"created_at": "2023-11-07T05:31:56Z"
}
]
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The member cluster.
Response
The pool that remains.
The organisation's CI cluster pool: the clusters its pipeline runs are spread across. Each run is pinned, at its first dispatch, to the least-loaded member whose agent can take a step, preferring the member where the repository last ran when the loads are within a fifth of a cluster's workers; a run never moves between clusters.