Available Events
The following events are available for subscriptions.
producedby | type | action | Corresponding API |
---|---|---|---|
BSSH | bssh.runs | statuschanged | Custom |
BSSH | bssh.sequencingstats | updated | Custom |
Genomic Data Store | gds.volumes | created | /v1/volumes |
Genomic Data Store | gds.folders | created | /v1/folders, any autocreated folders |
Genomic Data Store | gds.files | uploaded | /v1/files + s3 upload, s3 upload through folder upload credentials |
Genomic Data Store | gds.files | deleted | /v1/files/{id}:destroy |
Genomic Data Store | gds.files | archived | /v1/files/{id}:archive |
Genomic Data Store | gds.files | unarchived | /v1/files/{id}:unarchive |
Genomic Data Store | gds.folders | archived | /v1/folders/{id}:archive |
Genomic Data Store | gds.folders | unarchived | /v1/folders/{id}:unarchive |
Genomic Data Store | gds.folders | archiving | /v1/folders/{id}:archive |
Genomic Data Store | gds.folders | unarchiving | /v1/folders/{id}:unarchive |
Genomic Data Store | gds.folders | deleting | /v1/folders/{id}:delete |
Genomic Data Store | gds.folders | deleted | /v1/folders/{id}:delete |
Genomic Sequencing Service | gss.analysisRuns | samplesRegistered | /v1/sequencing/analysisRuns/{id} |
Genomic Sequencing Service | gss.samples | dataAdded | /v1/sequencing/samples/{id} |
Task Execution Service | tes.runs | created | /v1/tasks/runs/{id} |
Task Execution Service | tes.runs | updated | /v1/tasks/runs/{id} |
Task Execution Service | tes.runs | abort | /v1/tasks/runs/{id} |
Workflow Execution Service | wes.runs | created | /v1/workflows/runs/{id} |
Workflow Execution Service | wes.runs | updated (1) | /v1/workflows/runs/{id} |
Workflow Execution Service | wes.runs | aborted | /v1/workflows/runs/{id} |
Workflow Execution Service | wes.runs.historyevents | started | /v1/workflows/runs/{id} |
Workflow Execution Service | wes.runs.historyevents | succeeded | /v1/workflows/runs/{id} |
Workflow Execution Service | wes.runs.historyevents | failed | /v1/workflows/runs/{id} |
Workflow Execution Service | wes.workflows | created | /v1/workflows |
Workflow Execution Service | wes.workflows | updated | /v1/workflows/{id} |
Workflow Execution Service | wes.versions | created | /v1/workflows and /v1/workflows/{id}/versions |
Workflow Execution Service | wes.versions | updated | /v1/workflows/{id}/versions/{version} |
The producedby, type, and action fields shown in the table are included as SQS and SNS message attributes. The response contains the same structure and contents as performing a GET request to the corresponding API, however some fields might be omitted to prevent exceed payload size limits. For example, the definition
, input
, and output
fields in the WES workflow run model are excluded from the wes.runs
event.
The majority of actions performed on services are exposed as events.
(1) The RunSucceeded event does not contain the Output payload due to its potential for being very large
Last updated