record_deployment

Put a deployment on record. Give project_id, environment_id (one of the project's, from list_environments) and version (a tag, a semantic version or a build number), and commit_sha, branch, pipeline_url, notes, started_at and finished_at when you know them. The status is succeeded when left out, so a deployment done by hand is recorded in one call; queued, running or failed record where things stand instead, and a deployment opened as running is finished by the pipeline over REST, not through this tool. A succeeded deployment writes the version and its own id onto the environment, and the record is written as the person the token acts as, with the source ci. The event for the status goes out, and a failed deployment, or one that reached production, tells the project's leads. The same record POST /v1/projects/{project}/deployments writes. It needs deployment:record; a client guest's token is refused.