Skip to main content
POST
Propose a cluster access policy change

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

authorization
string | null
x-ankra-organisation-id
string | null

Body

application/json
reason
string
required

Why the policy should change; the owner or admin who applies the proposal reads it. Whitespace alone is refused.

Required string length: 3 - 500
creator_grant_role
enum<string>

Omitted keeps the current value.

Available options:
none,
view,
edit,
admin,
cluster-admin
max_grant_role
enum<string>

Omitted keeps the current value.

Available options:
view,
edit,
admin,
cluster-admin
elevated_max_ttl_seconds
integer | null

null clears the bound; omitting the field keeps the current value.

Required range: 60 <= x <= 31536000
require_reason_from_role
enum<string> | null

null clears the bound; omitting the field keeps the current value.

Available options:
view,
edit,
admin,
cluster-admin

Response

Successful Response

id
string<uuid>
required
status
enum<string>
required

A pending proposal past expires_at reads as expired.

Available options:
pending,
applied,
dismissed,
expired,
superseded
proposed
ProposedClusterAccessPolicy · object
required
base
ClusterAccessPolicy · object
required
current
ClusterAccessPolicy · object
required
base_matches_current
boolean
required

false means the policy changed since the proposal was made, and applying it answers 409 policy_changed.

reason
string
required
proposed_by
ClusterAccessPolicyProposalPrincipal · object
required
created_at
string<date-time>
required
expires_at
string<date-time>
required
decided_by_user_id
string<uuid> | null
required
decided_at
string<date-time> | null
required
decision_note
string | null
required
apply_url
string
required

The Ankra web app page (Organisation > Roles, with ?org= and ?proposal=) an owner or admin applies the proposal from, signed in.