Skip to main content

Get the cluster-profile templates behind a held update

GET 

/v1/edge-mgmt/cluster/update-lock/held-profile

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.

Responses​

The held profile and the profile in force, or pending false when nothing is held