DeleteVirtualMachineRestore
Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ”Define the version of the Connect protocol
Define the timeout, in ms
Request Body required
Section titled “Request Body required ”object
Responses
Section titled “ Responses ”Success
A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:
service Foo {
rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
}object
default
Section titled “default ”Error
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
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.
A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
object
A URL that acts as a globally unique identifier for the type of the serialized message. For example: type.googleapis.com/google.rpc.ErrorInfo. This is used to determine the schema of the data in the value field and is the discriminator for the debug field.
The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the type field.
Detailed error information.