Skip to main content
GET
Get who runs each environment (browser session)

Authorizations

ankra_session
string
cookie
required

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

Path Parameters

application_id
string
required

Response

Successful Response

application_id
string
required
storage
enum<string>
required

stored: at least one stored layer (organisation, application or one of its environments) applies; seeded: every layer is read from existing settings; unknown: the stored layers could not be read, so read_state is unknown too. Per area, source.layer names the layer that decided it and seeded_from the setting a seed came from.

Available options:
seeded,
stored,
unknown
read_state
enum<string>
required
Available options:
ok,
partial,
unknown
read_reason
string
required
unread
enum<string>[]
required
Available options:
auto_remediation_policy,
cost_autopilot_tier,
deploys_on_push
environments
ApplicationAutonomyEnvironment · object[]
required
layers
ApplicationAutonomyStoredLayers · object | null
required

What is stored for the application, the layers a write starts from. null when the stored layers were not read; no write may be built then.

choices_take_effect_areas
enum<string>[]
required

The areas whose stored choice Ankra honours today. The autonomous lane of each consults the stored levels before it acts, holding itself at a lower choice and never acting above its own setting, or, for keep_it_safe, acts only when a person asks, so every stored level already holds. A choice in any other area is stored and shown, but no lane acts on it yet.

Available options:
keep_it_up,
ship_changes,
keep_it_safe,
keep_costs_down,
keep_it_current,
fix_my_code
pause
ApplicationAutonomyPauseSummary · object
required

Whether a person paused Ankra's autonomous actions for the application, as GET /org/applications/{application_id}/autonomy-pause answers it. Read on its own, so it is answered even when read_state is unknown; its own read_state is unknown, with paused null, when the pause could not be read.

application_wide
ApplicationAutonomyApplicationWide · object
required

What governs a lane acting for the whole application: the application-wide gate's own answer for keep_it_safe, which the security lane's fix to the repository reads, and for fix_my_code, which the build-fixing lane's fix reads, each reaching every environment at once. Every other area's lane reads its own environment's setting, so environments carries those and this answer leaves them out. It is compared against the environments that place the application, and can differ from the level each entry of environments shows, in either direction: an environment where only weak evidence puts the application (a stray add-on of its chart, or a draft, on a cluster a person confirmed as staging) may hold it back but never loosen it, an environment that places nothing governs nothing until something is placed there, apart from a choice stored on it, and the strictest environment holds the others. Its level is never looser than the level any entry of environments that places the application shows for the area. Read on its own on the primary database, so it already shows a choice stored just before, and answered even when read_state is unknown; its own read_state is unknown, with no areas, when it could not be read.

limits_editable
boolean
required

The write supports transactional expected-layer comparisons. This is not a claim that automatic lanes enforce limits.