services.release.manage

Generated at from openvibe-contracts v0.114.0 and openvibe-sdk v0.35.1.

Grantable to apps: request it for an app on its project page. Network approves it only inside the project's allowance.

An app manages release metadata for ITSELF with its own token (audience openvibe.services): create a release from a validated app or mod manifest, publish, deprecate (with a reason and an optional replacement) and revoke it. The token's sub must be app:<the app in the path>; people manage releases in the console at openvibe.services with their project role instead. Trust tiers are not part of this capability (staff metadata only).

Owner
services (token audience openvibe.services)
Version
1.0
Status
active
Visibility
public
Resource constraints
owner, project
Quota class
services-release-write
Permissions
services:releases:write
Input
services.release-manage-request@1
Output
services.release-manage-result@1
Events
services.app.published, services.app.deprecated, services.app.revoked
Implemented by
  • POST /api/v1/apps/:app/releases
  • POST /api/v1/releases/:id/publish
  • POST /api/v1/releases/:id/deprecate
  • POST /api/v1/releases/:id/revoke

These routes in the API explorer