Update all json files; make some fixes to make it work at all

This commit is contained in:
Sebastian Thiel
2022-03-08 07:59:31 +08:00
parent d12cd3238e
commit 743a56f4b7
372 changed files with 256017 additions and 32197 deletions

View File

@@ -3,7 +3,7 @@
"oauth2": {
"scopes": {
"https://www.googleapis.com/auth/cloud-platform": {
"description": "See, edit, configure, and delete your Google Cloud Platform data"
"description": "See, edit, configure, and delete your Google Cloud data and see the email address for your Google Account."
},
"https://www.googleapis.com/auth/genomics": {
"description": "View and manage Genomics data"
@@ -199,7 +199,7 @@
],
"parameters": {
"filter": {
"description": "A string for filtering Operations. In v2alpha1, the following filter fields are supported: * createTime: The time this job was created * events: The set of event (names) that have occurred while running the pipeline. The : operator can be used to determine if a particular event has occurred. * error: If the pipeline is running, this value is NULL. Once the pipeline finishes, the value is the standard Google error code. * labels.key or labels.\"key with space\" where key is a label key. * done: If the pipeline is running, this value is false. Once the pipeline finishes, the value is true. In v1 and v1alpha2, the following filter fields are supported: * projectId: Required. Corresponds to OperationMetadata.projectId. * createTime: The time this job was created, in seconds from the [epoch](http://en.wikipedia.org/wiki/Unix_time). Can use `>=` and/or `<=` operators. * status: Can be `RUNNING`, `SUCCESS`, `FAILURE`, or `CANCELED`. Only one status may be specified. * labels.key where key is a label key. Examples: * `projectId = my-project AND createTime >= 1432140000` * `projectId = my-project AND createTime >= 1432140000 AND createTime <= 1432150000 AND status = RUNNING` * `projectId = my-project AND labels.color = *` * `projectId = my-project AND labels.color = red`",
"description": "A string for filtering Operations. In v2alpha1, the following filter fields are supported: * createTime: The time this job was created * events: The set of event (names) that have occurred while running the pipeline. The : operator can be used to determine if a particular event has occurred. * error: If the pipeline is running, this value is NULL. Once the pipeline finishes, the value is the standard Google error code. * labels.key or labels.\"key with space\" where key is a label key. * done: If the pipeline is running, this value is false. Once the pipeline finishes, the value is true. Examples: * `projectId = my-project AND createTime >= 1432140000` * `projectId = my-project AND createTime >= 1432140000 AND createTime <= 1432150000 AND status = RUNNING` * `projectId = my-project AND labels.color = *` * `projectId = my-project AND labels.color = red`",
"location": "query",
"type": "string"
},
@@ -301,7 +301,7 @@
}
}
},
"revision": "20210324",
"revision": "20220302",
"rootUrl": "https://genomics.googleapis.com/",
"schemas": {
"Accelerator": {
@@ -335,6 +335,10 @@
"$ref": "Secret",
"description": "If the specified image is hosted on a private registry other than Google Container Registry, the credentials required to pull the image must be specified here as an encrypted secret. The secret must decrypt to a JSON-encoded dictionary containing both `username` and `password` keys."
},
"encryptedEnvironment": {
"$ref": "Secret",
"description": "The encrypted environment to pass into the container. This environment is merged with values specified in the google.genomics.v2alpha1.Pipeline message, overwriting any duplicate values. The secret must decrypt to a JSON-encoded dictionary where key-value pairs serve as environment variable names and their values. The decoded environment variables can overwrite the values specified by the `environment` field."
},
"entrypoint": {
"description": "If specified, overrides the `ENTRYPOINT` specified in the container.",
"type": "string"
@@ -490,32 +494,6 @@
},
"type": "object"
},
"ComputeEngine": {
"description": "Describes a Compute Engine resource that is being managed by a running pipeline.",
"id": "ComputeEngine",
"properties": {
"diskNames": {
"description": "The names of the disks that were created for this pipeline.",
"items": {
"type": "string"
},
"type": "array"
},
"instanceName": {
"description": "The instance on which the operation is running.",
"type": "string"
},
"machineType": {
"description": "The machine type of the instance.",
"type": "string"
},
"zone": {
"description": "The availability zone in which the instance resides.",
"type": "string"
}
},
"type": "object"
},
"ContainerKilledEvent": {
"description": "An event generated when a container is forcibly terminated by the worker. Currently, this only occurs when the container outlives the timeout specified by the user.",
"id": "ContainerKilledEvent",
@@ -713,7 +691,7 @@
"The caller does not have permission to execute the specified operation. `PERMISSION_DENIED` must not be used for rejections caused by exhausting some resource (use `RESOURCE_EXHAUSTED` instead for those errors). `PERMISSION_DENIED` must not be used if the caller can not be identified (use `UNAUTHENTICATED` instead for those errors). This error code does not imply the request is valid or the requested entity exists or satisfies other pre-conditions. HTTP Mapping: 403 Forbidden",
"The request does not have valid authentication credentials for the operation. HTTP Mapping: 401 Unauthorized",
"Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space. HTTP Mapping: 429 Too Many Requests",
"The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`: (a) Use `UNAVAILABLE` if the client can retry just the failing call. (b) Use `ABORTED` if the client should retry at a higher level (e.g., when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence). (c) Use `FAILED_PRECONDITION` if the client should not retry until the system state has been explicitly fixed. E.g., if an \"rmdir\" fails because the directory is non-empty, `FAILED_PRECONDITION` should be returned since the client should not retry unless the files are deleted from the directory. HTTP Mapping: 400 Bad Request",
"The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`: (a) Use `UNAVAILABLE` if the client can retry just the failing call. (b) Use `ABORTED` if the client should retry at a higher level. For example, when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence. (c) Use `FAILED_PRECONDITION` if the client should not retry until the system state has been explicitly fixed. For example, if an \"rmdir\" fails because the directory is non-empty, `FAILED_PRECONDITION` should be returned since the client should not retry unless the files are deleted from the directory. HTTP Mapping: 400 Bad Request",
"The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. See the guidelines above for deciding between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`. HTTP Mapping: 409 Conflict",
"The operation was attempted past the valid range. E.g., seeking or reading past end-of-file. Unlike `INVALID_ARGUMENT`, this error indicates a problem that may be fixed if the system state changes. For example, a 32-bit file system will generate `INVALID_ARGUMENT` if asked to read at an offset that is not in the range [0,2^32-1], but it will generate `OUT_OF_RANGE` if asked to read from an offset past the current file size. There is a fair bit of overlap between `FAILED_PRECONDITION` and `OUT_OF_RANGE`. We recommend using `OUT_OF_RANGE` (the more specific error) when it applies so that callers who are iterating through a space can easily look for an `OUT_OF_RANGE` error to detect when they are done. HTTP Mapping: 400 Bad Request",
"The operation is not implemented or is not supported/enabled in this service. HTTP Mapping: 501 Not Implemented",
@@ -868,87 +846,6 @@
},
"type": "object"
},
"OperationEvent": {
"description": "An event that occurred during an Operation.",
"id": "OperationEvent",
"properties": {
"description": {
"description": "Required description of event.",
"type": "string"
},
"endTime": {
"description": "Optional time of when event finished. An event can have a start time and no finish time. If an event has a finish time, there must be a start time.",
"format": "google-datetime",
"type": "string"
},
"startTime": {
"description": "Optional time of when event started.",
"format": "google-datetime",
"type": "string"
}
},
"type": "object"
},
"OperationMetadata": {
"description": "Metadata describing an Operation.",
"id": "OperationMetadata",
"properties": {
"clientId": {
"description": "This field is deprecated. Use `labels` instead. Optionally provided by the caller when submitting the request that creates the operation.",
"type": "string"
},
"createTime": {
"description": "The time at which the job was submitted to the Genomics service.",
"format": "google-datetime",
"type": "string"
},
"endTime": {
"description": "The time at which the job stopped running.",
"format": "google-datetime",
"type": "string"
},
"events": {
"description": "Optional event messages that were generated during the job's execution. This also contains any warnings that were generated during import or export.",
"items": {
"$ref": "OperationEvent"
},
"type": "array"
},
"labels": {
"additionalProperties": {
"type": "string"
},
"description": "Optionally provided by the caller when submitting the request that creates the operation.",
"type": "object"
},
"projectId": {
"description": "The Google Cloud Project in which the job is scoped.",
"type": "string"
},
"request": {
"additionalProperties": {
"description": "Properties of the object. Contains field @type with type URL.",
"type": "any"
},
"description": "The original request that started the operation. Note that this will be in current version of the API. If the operation was started with v1beta2 API and a GetOperation is performed on v1 API, a v1 request will be returned.",
"type": "object"
},
"runtimeMetadata": {
"additionalProperties": {
"description": "Properties of the object. Contains field @type with type URL.",
"type": "any"
},
"description": "Runtime metadata on this Operation.",
"type": "object"
},
"startTime": {
"description": "The time at which the job began to run.",
"format": "google-datetime",
"type": "string"
}
},
"type": "object"
},
"PersistentDisk": {
"description": "Configuration for a persistent disk to be attached to the VM. See https://cloud.google.com/compute/docs/disks/performance for more information about disk type, size, and performance considerations.",
"id": "PersistentDisk",
@@ -980,6 +877,10 @@
},
"type": "array"
},
"encryptedEnvironment": {
"$ref": "Secret",
"description": "The encrypted environment to pass into every action. Each action can also specify its own encrypted environment. The secret must decrypt to a JSON-encoded dictionary where key-value pairs serve as environment variable names and their values. The decoded environment variables can overwrite the values specified by the `environment` field."
},
"environment": {
"additionalProperties": {
"type": "string"
@@ -1078,17 +979,6 @@
"properties": {},
"type": "object"
},
"RuntimeMetadata": {
"description": "Runtime metadata that will be populated in the runtimeMetadata field of the Operation associated with a RunPipeline execution.",
"id": "RuntimeMetadata",
"properties": {
"computeEngine": {
"$ref": "ComputeEngine",
"description": "Execution information specific to Google Compute Engine."
}
},
"type": "object"
},
"Secret": {
"description": "Holds encrypted information that is only decrypted and stored in RAM by the worker VM when running the pipeline.",
"id": "Secret",
@@ -1251,6 +1141,10 @@
"description": "If true, allocate a preemptible VM.",
"type": "boolean"
},
"reservation": {
"description": "If specified, the VM will only be allocated inside the matching reservation. It will fail if the VM parameters don't match the reservation.",
"type": "string"
},
"serviceAccount": {
"$ref": "ServiceAccount",
"description": "The service account to install on the VM. This account does not need any permissions other than those required by the pipeline."