Alphaus Operations API
(BETA) Long operations API. Base URL: https://api.alphaus.cloud/m/blue
(BETA) Long operations API. Base URL: https://api.alphaus.cloud/m/blue
swagger: '2.0'
info:
title: Blue API reference Admin Operations API
description: 'Alphaus provides an API for interacting with its services. Blue API is a RESTful API that
can be accessed by an HTTP client such as `curl`, or any HTTP library which is part of most modern
programming languages. This API reference is autogenerated from [protocol buffers](https://developers.google.com/protocol-buffers)
defined in this [repository](https://github.com/alphauslabs/blueapi), together with our supported
[client libraries](https://alphauslabs.github.io/docs/blueapi/client-sdks/). See the official [documentation](https://alphauslabs.github.io/docs/blueapi/overview/)
for more information.
You may encounter the following feature maturity indicators:
- **(WORK-IN-PROGRESS)** - Development is ongoing, don''t use yet;
- **(BETA)** - New or experimental features, subject to changes; and
- **(DEPRECATED)** - Outdated or replaced features.
Some endpoints, especially those that return lists of resources, have streaming responses; newline-separated
stream of “chunks”. Each chunk is an envelope that can contain either a response message or an error.
Only the last chunk will include an error, if any.'
version: v1
host: api.alphaus.cloud
basePath: /m/blue
schemes:
- https
consumes:
- application/json
produces:
- application/json
tags:
- name: Operations
description: '(BETA) Long operations API. Base URL: https://api.alphaus.cloud/m/blue'
externalDocs:
description: Service definition
url: https://github.com/alphauslabs/blueapi/tree/main/operations/
paths:
/ops/v1:
get:
summary: Lists long-running operations.
operationId: Operations_ListOperations
responses:
'200':
description: A successful response.(streaming responses)
schema:
type: object
properties:
result:
$ref: '#/definitions/protosOperation'
error:
$ref: '#/definitions/rpcStatus'
title: Stream result of protosOperation
default:
description: An unexpected error response.
schema:
$ref: '#/definitions/rpcStatus'
parameters:
- name: parent
description: Optional. The name of the operation's parent resource. Not used at the moment.
in: query
required: false
type: string
- name: asOf
description: 'Optional. List operations on and after this date. Format is yyyymmdd. For example,
if you want to list all operations starting from June 01, 2021, set to `20210601`.
If not set, defaults to the first day of the current UTC month.'
in: query
required: false
type: string
- name: includeDone
description: 'Optional. If true, include all operations that are marked as done. Exclude by
default.'
in: query
required: false
type: boolean
tags:
- Operations
/ops/v1/{name}:
get:
summary: 'Gets the latest state of a long-running operation. You can use this method to
poll the operation result at intervals.'
operationId: Operations_GetOperation
responses:
'200':
description: A successful response.
schema:
$ref: '#/definitions/protosOperation'
default:
description: An unexpected error response.
schema:
$ref: '#/definitions/rpcStatus'
parameters:
- name: name
description: The name of the operation resource.
in: path
required: true
type: string
tags:
- Operations
delete:
summary: 'Deletes a long-running operation. This method indicates that the client is no
longer interested in the operation result. It does not cancel the operation.'
operationId: Operations_DeleteOperation
responses:
'200':
description: A successful response.
schema:
type: object
properties: {}
default:
description: An unexpected error response.
schema:
$ref: '#/definitions/rpcStatus'
parameters:
- name: name
description: The name of the operation resource to be deleted.
in: path
required: true
type: string
tags:
- Operations
/ops/v1/{name}:cancel:
post:
summary: 'Starts asynchronous cancellation on a long-running operation. The server makes
a best effort to cancel the operation, but success is not guaranteed. On successful
cancellation, the operation is not deleted; instead, it becomes an operation with
a value of [google.rpc.Status.code][google.rpc.Status.code] 1, corresponding
to `Code.CANCELLED`.'
operationId: Operations_CancelOperation
responses:
'200':
description: A successful response.
schema:
type: object
properties: {}
default:
description: An unexpected error response.
schema:
$ref: '#/definitions/rpcStatus'
parameters:
- name: name
description: The name of the operation resource to be cancelled.
in: path
required: true
type: string
- name: body
in: body
required: true
schema:
$ref: '#/definitions/OperationsCancelOperationBody'
tags:
- Operations
definitions:
rpcStatus:
type: object
properties:
code:
type: integer
format: int32
description: The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message:
type: string
description: 'A developer-facing error message, which should be in English. Any
user-facing error message should be localized and sent in the
[google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.'
details:
type: array
items:
type: object
$ref: '#/definitions/protobufAny'
description: 'A list of messages that carry the error details. There is a common set of
message types for APIs to use.'
description: 'The `Status` type defines a logical error model that is suitable for
different programming environments, including REST APIs and RPC APIs. It is
used by [gRPC](https://github.com/grpc). Each `Status` message contains
three pieces of data: error code, error message, and error details.
You can find out more about this error model and how to work with it in the
[API Design Guide](https://cloud.google.com/apis/design/errors).'
protosOperation:
type: object
properties:
name:
type: string
description: The server-assigned name.
metadata:
$ref: '#/definitions/protobufAny'
description: 'Service-specific metadata associated with the operation. It typically
contains progress information and common metadata such as create time.
Some services might not provide such metadata. Any method that returns a
long-running operation should document the metadata type, if any.'
done:
type: boolean
description: 'If the value is `false`, it means the operation is still in progress.
If `true`, the operation is completed, and either `error` or `response` is
available.'
error:
$ref: '#/definitions/rpcStatus'
description: The error result of the operation in case of failure or cancellation.
response:
$ref: '#/definitions/protobufAny'
description: 'The normal response of the operation in case of success. If the original method
returns
no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the
original method is standard `Get`/`Create`/`Update`, the response should be the
resource. For other methods, the response should have the type `XxxResponse`, where
`Xxx` is the original method name. For example, if the original method name is
`TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.'
description: 'This resource represents a long-running operation that is the result of a
network API call.'
OperationsCancelOperationBody:
type: object
description: Request message for the Operations.CancelOperation rpc.
protobufAny:
type: object
properties:
'@type':
type: string
description: "A URL/resource name that uniquely identifies the type of the serialized\nprotocol\
\ buffer message. This string must contain at least\none \"/\" character. The last segment of\
\ the URL's path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`).\
\ The name should be in a canonical form\n(e.g., leading \".\" is not accepted).\n\nIn practice,\
\ teams usually precompile into the binary all types that they\nexpect it to use in the context\
\ of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally\
\ set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme\
\ is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n\
\ value in binary format, or produce an error.\n* Applications are allowed to cache lookup\
\ results based on the\n URL, or have them precompiled into a binary to avoid any\n lookup.\
\ Therefore, binary compatibility needs to be preserved\n on changes to types. (Use versioned\
\ type names to manage\n breaking changes.)\n\nNote: this functionality is not currently available\
\ in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com.\
\ As of May 2023, there are no widely used type server\nimplementations and no plans to implement\
\ one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation\
\ specific semantics."
additionalProperties: {}
description: "`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that\
\ describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack\
\ Any values in the form\nof utility functions or additional generated methods of the Any type.\n\
\nExample 1: Pack and unpack a message in C++.\n\n Foo foo = ...;\n Any any;\n any.PackFrom(foo);\n\
\ ...\n if (any.UnpackTo(&foo)) {\n ...\n }\n\nExample 2: Pack and unpack a message\
\ in Java.\n\n Foo foo = ...;\n Any any = Any.pack(foo);\n ...\n if (any.is(Foo.class))\
\ {\n foo = any.unpack(Foo.class);\n }\n // or ...\n if (any.isSameTypeAs(Foo.getDefaultInstance()))\
\ {\n foo = any.unpack(Foo.getDefaultInstance());\n }\n\n Example 3: Pack and unpack a message\
\ in Python.\n\n foo = Foo(...)\n any = Any()\n any.Pack(foo)\n ...\n if any.Is(Foo.DESCRIPTOR):\n\
\ any.Unpack(foo)\n ...\n\n Example 4: Pack and unpack a message in Go\n\n foo :=\
\ &pb.Foo{...}\n any, err := anypb.New(foo)\n if err != nil {\n ...\n }\n \
\ ...\n foo := &pb.Foo{}\n if err := any.UnmarshalTo(foo); err != nil {\n ...\n \
\ }\n\nThe pack methods provided by protobuf library will by default use\n'type.googleapis.com/full.type.name'\
\ as the type URL and the unpack\nmethods only use the fully qualified type name after the last\
\ '/'\nin the type URL, for example \"foo.bar.com/x/y.z\" will yield type\nname \"y.z\".\n\nJSON\n\
====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized,\
\ embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n\
\ package google.profile;\n message Person {\n string first_name = 1;\n string last_name\
\ = 2;\n }\n\n {\n \"@type\": \"type.googleapis.com/google.profile.Person\",\n \"\
firstName\": <string>,\n \"lastName\": <string>\n }\n\nIf the embedded message type is well-known\
\ and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value`\
\ which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\
\n {\n \"@type\": \"type.googleapis.com/google.protobuf.Duration\",\n \"value\": \"\
1.212s\"\n }"
servers:
- url: https://api.alphaus.cloud/m/blue
description: Base URL reconciled from apis.yml