Skip to main content

AcknowledgeConfigDifference

POST 
/admin/v1/customers/:customer_id/config-differences/:id:acknowledge

Acknowledge one configuration difference, which takes it off the default view of the data plane or the project it reads on. The entry itself stays: nothing here deletes the record that the fleet was once split.

Acknowledging an entry a second time changes nothing and reports acknowledged: false, so the ledger keeps naming whoever actually looked.

A project owner answers the entries ListProjectConfigDifferences shows them by naming their project in project_id, which is what binds the gate to it. An administrator answers either list and leaves project_id empty.

Request​

Responses​

Success