Move an install to the registration head
Records the account against the deployment's current release and contract version. {"is_pinned": true} freezes it there, so a later release does not move this account; {"is_pinned": false} releases the freeze.
No hooks fire. An upgrade changes which contract version the account is recorded against, and nothing else — re-running the seeding hook on every upgrade would re-seed an account that already has its rows. An app with per-version work to do has reconcile, which is triggered deliberately.
Request
- Base URL: https://api.atlan.com (the document declares no server; this is the origin it was published from)
- URL: https://api.atlan.com/registry/v1/apps/{app}/upgrade
- Auth: HTTP bearer
Path parameters
The app's name, which is the extension's name.
Headers
Codings applied to the request body, outermost last. Send base64, or gzip, base64 to compress first; the body is decoded before it is read and Content-Type still names the inner media type. Omit for an unencoded body.
Request body
Response
OK
Changes
No recorded changes to this operation across all 1 revision of this API.