Skip to main content

PlanCatalogSync

POST 
/admin/v1/catalog/sync:plan

PlanCatalogSync fetches the published catalogue and returns what a sync would do, writing nothing to the catalogue itself.

It DOES advance the sync-state record's checked_* fields, exactly as a CLI dry run does -- that record is what a dashboard's "new models available" indicator reads, and a preview is precisely "this plane checked the published catalogue". Hence models:EDIT rather than READ: the RPC writes the same record RecordCatalogSync writes, so it carries the same atom.

Request​

Responses​

Success