plugin

Privacy disclosure status for an installed plugin

What the operator accepted at install, what the next upgrade would land (from the fetched upstream tip, else the listing, else the installed file), and whether the two differ in the keys that re-show the install dialog: the whole block minus summary (sends, collects, sensors, remoteAccess, systemChanges, closedCode, and other -- trimmed, "none" read as empty); keys outside that list are ignored. Reads the already-fetched upstream tip; call POST /plugin/{RepoName}/updates first to fetch. An upgrade whose declaration changed is refused unless the request body carries {"privacyAccepted": <the pending block>}. ?target=reinstall diffs the block a Reinstall would land instead (the versions[] branch and pinned sha selected for this FPP, which after an FPP major upgrade may differ from the checked-out branch) and adds reinstallTarget: {branch, sha}, the server's selection, which the Plugins page posts back as the install's branch and sha so the block diffed and the commit cloned are the same one.

get/api/plugin/{RepoName}/privacy

Query parameters

target'upgrade' | 'reinstall'

Which operation's incoming block to diff: upgrade (origin/<checked-out branch>) or reinstall (the versions[] branch/sha for this FPP).

Response

Privacy status

object required

Changes