Install a plugin from a registry
POST/plugins/:id/install
Downloads the release, checks its sha256 and signature against the keys of the registry it comes from, loads it, grants the capabilities it declares and starts it along with any installed dependency that is off. Without a version the newest compatible release is used; naming an older one pins the plugin there. A bundled plugin at its shipped version needs no download. capabilities must list exactly what the consent prompt showed; when it differs from what the release asks for, nothing is downloaded and the answer is 409 CONSENT_MISMATCH with the real list.
Request
Responses
- 200
- 400
- 403
- 404
- 409
- 502
The installed version and the plugin's state.
Invalid id, version or capability list, or no capability list.
The caller lacks admin.plugins.manage.
Not in that registry.
Already installed, incompatible, the consent does not match, the registry is off, the id belongs to an official plugin, or managed by a linked server.
The registry could not be reached.