chore: Update discovery artifacts (#1328)
## Deleted keys were detected in the following stable discovery artifacts:
admindirectoryv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/1feda6f78f168e28d7842f49ad91fb00dc24ec19)
bigqueryreservationv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
computev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
doubleclickbidmanagerv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
doubleclickbidmanagerv11[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
serviceconsumermanagementv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceusagev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
## Deleted keys were detected in the following pre-stable discovery artifacts:
bigqueryreservationv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
computealpha[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
computebeta[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
serviceconsumermanagementv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceusagev1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
## Discovery Artifact Change Summary:
admindirectoryv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/1feda6f78f168e28d7842f49ad91fb00dc24ec19)
bigqueryreservationv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
bigqueryreservationv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
computealpha[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
computebeta[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
computev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
containerv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/9bc4a12e7ab57a1b5a5d3637087b80b3008e3352)
containerv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/9bc4a12e7ab57a1b5a5d3637087b80b3008e3352)
doubleclickbidmanagerv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
doubleclickbidmanagerv11[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
serviceconsumermanagementv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceconsumermanagementv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceusagev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
serviceusagev1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
diff --git a/googleapiclient/discovery_cache/documents/container.v1beta1.json b/googleapiclient/discovery_cache/documents/container.v1beta1.json
index 628074f..a7b5ee8 100644
--- a/googleapiclient/discovery_cache/documents/container.v1beta1.json
+++ b/googleapiclient/discovery_cache/documents/container.v1beta1.json
@@ -2484,7 +2484,7 @@
}
}
},
- "revision": "20210413",
+ "revision": "20210419",
"rootUrl": "https://container.googleapis.com/",
"schemas": {
"AcceleratorConfig": {
@@ -3119,6 +3119,10 @@
"$ref": "AddonsConfig",
"description": "Configurations for the various addons available to run in the cluster."
},
+ "desiredAutopilot": {
+ "$ref": "Autopilot",
+ "description": "The desired Autopilot configuration for the cluster."
+ },
"desiredBinaryAuthorization": {
"$ref": "BinaryAuthorization",
"description": "The desired configuration options for the Binary Authorization feature."
@@ -5464,7 +5468,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",
@@ -5670,7 +5674,7 @@
"description": "The release channel of the version. If empty, it means a non-channel release."
},
"resource": {
- "description": "Optional. Optional relative path to the resource. For example, the relative path of the node pool.",
+ "description": "Optional relative path to the resource. For example, the relative path of the node pool.",
"type": "string"
},
"resourceType": {