Environments
Lists all environments
The bearer token can be obtained by creating a ServiceAccount.
Happy response.
Error object.
Creates a new environment.
The bearer token can be obtained by creating a ServiceAccount.
Sets the name of the new environment. It must be a valid HQ resource name: it can only contain lowercase alphanumeric characters or hyphens; hyphens cannot appear at the end or start; the length is 63 characters at most.
Sets the display name of the new environment. If not provided, the value of "name" will be used.
Enumerates Tiers.
Happy response.
Error object.
Retrieves a single environment by name.
The bearer token can be obtained by creating a ServiceAccount.
Happy response.
Error object.
Updates an environment.
The bearer token can be obtained by creating a ServiceAccount.
Enumerates Tiers.
Updates the display name of the environment.
Happy response.
Error object.
Deletes an environment.
The bearer token can be obtained by creating a ServiceAccount.
Successful deletion.
Error object.
No content
Provides Server-Sent Events (SSE) for environment updates. TODO.
The bearer token can be obtained by creating a ServiceAccount.
Error object.
Error object.
Proxies HTTP to a Lenses instance. Note: this is not a regular HTTP API endpoint. The path specified here is a prefix. Everything beneath it gets proxied to the corresponding Lenses instance. Any request body and method (the GET here is only a placeholder) are accepted, as long as the Lenses API accepts it. The connection can even be upgraded to a websocket. The status code and response body are controlled by the Lenses API. This concept does not fit into the OpenAPI world at all; this definition is only here for the sake of documentation to avoid having an undocumented dark matter API.
The bearer token can be obtained by creating a ServiceAccount.
Error object.
Error object.
Last updated
Was this helpful?