component.* events
The lifecycle of a project's components: creation, edits, archiving, restoring and deletion.
The lifecycle of a project's components: creation, edits, archiving, restoring and deletion. A component is one application the project is made of, so a mirror of the project record subscribes to this family beside project.* and environment.* to know what is being built and where it runs.
Every event in the family is scoped to the project, so project_id in the envelope is always set and an endpoint confined to one project receives only that project's events. The payloads are thin on purpose: the ids, the name and what the transition itself carries, never a snapshot of the component. Read the components endpoint for the record.
Background
Required ability
Tokens subscribing to component.* events need component:view at mint time.
Events
How is this guide?
Last updated on