Skip to main content

Take the cluster-profile update lock off, or put it back on

POST 

/v1/edge-mgmt/cluster/update-lock/gate

Works the update lock by hand: takes it off so the waiting profile applies on the next sync, or puts it back on to close a window that is already open. stylus-operator engages the lock and re-engages it by itself once a rollout finishes; these are the manual transitions, and this device is the only place either is reachable, because the Palette API has no equivalent and never will. Engaging re-locks only: it does not recall an update that has already been applied, and an update still rolling out continues. Asking for the gate the lock already has is not an error: that is a 200 carrying the state as it stands, and nothing is written, because restamping the transition would move the clock the operator's closing rule reads. Whether this call caused the state or found it is read from unlockedAt and engagedAt in the response, never from the status code.

Request​

Responses​

The gate state the lock now holds