Read how far the organization's closure has come
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/closure';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/closure \ --header 'Authorization: Bearer <token>'Any member. The state is active, closing or closed; while closing, the stage says what cleanup is doing, and the counts say what is left. The audit record shows kinds, counts and times, and is kept for audit_term_days after cleanup completes.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”Current state.
An organization’s state and how far its closure has come. Closing reads closed once every execution environment is gone and nothing is kept.
object
object
What is left, as counts.
object
Runs that have not ended yet; the closure asked each to cancel.
Runs that ended with an effect nobody could confirm, and no resolution yet.
Recovery checkpoints kept because a reconciliation or a hold still needs them.
Legal or security holds in force.
Execution environments still to be removed.
Checkpoints still stored, kept or not yet deleted.
Environment templates still to be removed.
Network policies still to be removed.
The cleanup of the organization’s execution environments.
object
object
What keeps the checkpoint: the run awaits reconciliation, or a hold names it.
One entry of the cleanup’s audit record: a kind, keyed counts and classes, and when. Never content.
object
object
How long a completed cleanup’s audit record is kept.
Example
{ "state": "active", "stage": "fencing", "sandboxes": { "phase": "runs", "retained": [ { "reason": "reconciliation" } ] }, "audit": [ { "kind": "cleanup_started", "detail": { "phase": "runs" } } ]}default
Section titled “default”Request rejected or unavailable.
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}