Skip to main content

Edge Mgmt

πŸ“„οΈ Take the cluster-profile update lock off ...

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.

πŸ“„οΈ Get the cluster-profile templates behind ...

Reports the cluster-profile templates behind a held update on this device: the profile hubble is serving while the lock holds it, in the same shape the archive endpoints serve, so the Local UI reviews a held update the way it reviews an uploaded configuration. The profile in force is not repeated here β€” it comes from the applications endpoint. Nothing held is a 200 with an empty heldProfile, not a 404. It is a separate path from the lock status on purpose: the status is polled every ten seconds and stays small, while this payload is fetched on demand when the operator asks to review the held update. Available only on this device, like the other lock operations.