本文へ移動
runlot
リファレンスAPIbug-reports

bug-reports

Covers 4 API operations in the bug-reports category.

MethodPathDescription
GET/v1/orgs/{orgSlug}/bug-reportsThe organization's bug reports
POST/v1/orgs/{orgSlug}/bug-reportsFile a bug report with its evidence
GET/v1/orgs/{orgSlug}/bug-reports/{reportId}One bug report with its replies and snapshot
DELETE/v1/orgs/{orgSlug}/bug-reports/{reportId}Delete a bug report and its snapshot

GET /v1/orgs/{orgSlug}/bug-reports

Needs the admin role.

operationId listBugReports

Status codeDescriptionResponse body
200Newest first, without snapshotsobject
403——
404——

POST /v1/orgs/{orgSlug}/bug-reports

runlot bug-report. The CLI sends references — request IDs, a window, its own last failed command — and Runlot resolves them and snapshots the result (the named invocation records with their events and spans, worker exits, failing invocations, active issues, the current and previous deployment, recent builds), so the evidence survives retention. noLogs attaches invocation skeletons and worker exits only. Secret-looking arguments and runlot.json values are redacted again on the server. You get an email with the report ID; replies arrive by email and on the report. Any member may file one about a project they can see.

operationId createBugReport

Request body: application/json · BugReportCreate

Status codeDescriptionResponse body
201The reportBugReport
400——
404——

GET /v1/orgs/{orgSlug}/bug-reports/{reportId}

Org admins and the person who filed it.

operationId getBugReport

ParameterLocationRequiredTypeDescription
snapshotqueryNostring0 leaves the snapshot out
Status codeDescriptionResponse body
200The reportBugReport
404——

DELETE /v1/orgs/{orgSlug}/bug-reports/{reportId}

Needs the admin role.

operationId deleteBugReport

Status codeDescriptionResponse body
204Deleted—
403——
404——

このページの目次