What the app lifecycle job would do now (admins)

GET

/api/workspaces/{workspaceId}/apps/lifecycle/plan

const url = 'http://localhost:8080/api/workspaces/example/apps/lifecycle/plan';
const options = {method: 'GET', headers: {cookie: 'auth_session=<auth_session>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url http://localhost:8080/api/workspaces/example/apps/lifecycle/plan \
  --cookie auth_session=<auth_session>

The daily lifecycle job’s plan for this workspace, computed now and changing nothing: apps it would notify as stale, archive, or whose binding schedules it would pause or resume. mode says whether the job only logs this plan (dry-run, the default) or applies it.

Authorizations

cookieAuth
bearerAuth

Parameters

Path Parameters

workspaceId

required

string

Responses

2XX

Successful response

application/json

object

success

Whether the request succeeded.

boolean

data

Endpoint-specific response payload.

message

string

error

string

Example

{
  "message": "Operation completed",
  "error": "Error message"
}

4XX

Invalid request

application/json

object

success

boolean

error

string

Example

{
  "error": "Error message"
}

5XX

Internal server error

application/json

object

success

boolean

error

string

Example

{
  "error": "Error message"
}