google-api-python-client 2.148.0__py2.py3-none-any.whl → 2.150.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/securitycenter.v1beta2.json

@@ -1993,7 +1993,7 @@
 }
 }
 },
-"revision": "20240918",
+"revision": "20241004",
 "rootUrl": "https://securitycenter.googleapis.com/",
 "schemas": {
 "Access": {
@@ -2291,6 +2291,10 @@
 "description": "Represents an Azure resource group.",
 "id": "AzureResourceGroup",
 "properties": {
+"id": {
+"description": "The ID of the Azure resource group.",
+"type": "string"
+},
 "name": {
 "description": "The name of the Azure resource group. This is not a UUID.",
 "type": "string"
@@ -2385,6 +2389,17 @@
 },
 "type": "object"
 },
+"CelPolicySpec": {
+"description": "YAML-based rule that uses CEL, which supports the declaration of variables and a filtering predicate. A vulnerable resource is emitted if the evaluation is false. Given: 1) the resource types as: - resource_types: \"compute.googleapis.com/Instance\" - resource_types: \"compute.googleapis.com/Firewall\" 2) the CEL policy spec as: name: bad_instance resource_filters: - name: instance resource_type: compute.googleapis.com/Instance filter: > instance.status == 'RUNNING' && 'public' in instance.tags.items - name: firewall resource_type: compute.googleapis.com/Firewall filter: > firewall.direction == 'INGRESS' && !firewall.disabled && firewall.allowed.exists(rule, rule.IPProtocol.upperAscii() in ['TCP', 'ALL'] && rule.ports.exists(port, network.portsInRange(port, '11-256'))) rule: match: - predicate: > instance.networkInterfaces.exists(net, firewall.network == net.network) output: > {'message': 'Compute instance with publicly accessible ports', 'instance': instance.name} Users are able to join resource types together using the exact format as Kubernetes Validating Admission policies.",
+"id": "CelPolicySpec",
+"properties": {
+"spec": {
+"description": "The CEL policy to evaluate to produce findings. A finding is generated when the policy validation evaluates to false.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "CloudArmor": {
 "description": "Fields related to Google Cloud Armor findings.",
 "id": "CloudArmor",
@@ -3782,6 +3797,10 @@
 "description": "Defines the properties in a custom module configuration for Security Health Analytics. Use the custom module configuration to create custom detectors that generate custom findings for resources that you specify.",
 "id": "GoogleCloudSecuritycenterV1CustomConfig",
 "properties": {
+"celPolicy": {
+"$ref": "CelPolicySpec",
+"description": "The CEL policy spec attached to the custom module."
+},
 "customOutput": {
 "$ref": "GoogleCloudSecuritycenterV1CustomOutputSpec",
 "description": "Custom output properties."
@@ -4864,6 +4883,10 @@
 "description": "Represents an Azure resource group.",
 "id": "GoogleCloudSecuritycenterV2AzureResourceGroup",
 "properties": {
+"id": {
+"description": "The ID of the Azure resource group.",
+"type": "string"
+},
 "name": {
 "description": "The name of the Azure resource group. This is not a UUID.",
 "type": "string"

googleapiclient/discovery_cache/documents/serviceconsumermanagement.v1.json

@@ -542,7 +542,7 @@
 }
 }
 },
-"revision": "20240919",
+"revision": "20240929",
 "rootUrl": "https://serviceconsumermanagement.googleapis.com/",
 "schemas": {
 "AddTenantProjectRequest": {
@@ -2037,7 +2037,7 @@
 "type": "object"
 },
 "Mixin": {
-"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inherting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
+"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inheriting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
 "id": "Mixin",
 "properties": {
 "name": {

googleapiclient/discovery_cache/documents/serviceconsumermanagement.v1beta1.json

@@ -715,7 +715,7 @@
 }
 }
 },
-"revision": "20240919",
+"revision": "20240929",
 "rootUrl": "https://serviceconsumermanagement.googleapis.com/",
 "schemas": {
 "Api": {
@@ -2086,7 +2086,7 @@
 "type": "object"
 },
 "Mixin": {
-"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inherting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
+"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inheriting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
 "id": "Mixin",
 "properties": {
 "name": {

googleapiclient/discovery_cache/documents/servicemanagement.v1.json

@@ -830,7 +830,7 @@
 }
 }
 },
-"revision": "20240920",
+"revision": "20240927",
 "rootUrl": "https://servicemanagement.googleapis.com/",
 "schemas": {
 "Advice": {
@@ -2636,7 +2636,7 @@
 "type": "object"
 },
 "Mixin": {
-"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inherting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
+"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inheriting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
 "id": "Mixin",
 "properties": {
 "name": {

googleapiclient/discovery_cache/documents/serviceusage.v1.json

@@ -426,7 +426,7 @@
 }
 }
 },
-"revision": "20240919",
+"revision": "20240929",
 "rootUrl": "https://serviceusage.googleapis.com/",
 "schemas": {
 "AddEnableRulesMetadata": {
@@ -2675,7 +2675,7 @@
 "type": "object"
 },
 "Mixin": {
-"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inherting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
+"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inheriting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
 "id": "Mixin",
 "properties": {
 "name": {

googleapiclient/discovery_cache/documents/serviceusage.v1beta1.json

@@ -964,7 +964,7 @@
 }
 }
 },
-"revision": "20240919",
+"revision": "20240929",
 "rootUrl": "https://serviceusage.googleapis.com/",
 "schemas": {
 "AddEnableRulesMetadata": {
@@ -3370,7 +3370,7 @@
 "type": "object"
 },
 "Mixin": {
-"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inherting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
+"description": "Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v1/{resource=**}:getAcl\"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = \"/v2/{resource=**}\"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inheriting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/{resource=**}:getAcl\"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\"; } ... }",
 "id": "Mixin",
 "properties": {
 "name": {

googleapiclient/discovery_cache/documents/sheets.v4.json

@@ -870,7 +870,7 @@
 }
 }
 },
-"revision": "20240917",
+"revision": "20241001",
 "rootUrl": "https://sheets.googleapis.com/",
 "schemas": {
 "AddBandingRequest": {
@@ -4195,7 +4195,7 @@
 "type": "string"
 },
 "visibility": {
-"description": "Limits the selected developer metadata to that which has a matching DeveloperMetadata.visibility. If left unspecified, all developer metadata visibile to the requesting project is considered.",
+"description": "Limits the selected developer metadata to that which has a matching DeveloperMetadata.visibility. If left unspecified, all developer metadata visible to the requesting project is considered.",
 "enum": [
 "DEVELOPER_METADATA_VISIBILITY_UNSPECIFIED",
 "DOCUMENT",

googleapiclient/discovery_cache/documents/spanner.v1.json

@@ -24,6 +24,11 @@
 "endpoints": [
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://spanner.europe-west8.rep.googleapis.com/",
+"location": "europe-west8"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://spanner.me-central2.rep.googleapis.com/",
 "location": "me-central2"
 },
@@ -49,13 +54,28 @@
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://spanner.us-south1.rep.googleapis.com/",
+"location": "us-south1"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://spanner.us-west1.rep.googleapis.com/",
 "location": "us-west1"
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://spanner.us-west2.rep.googleapis.com/",
+"location": "us-west2"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://spanner.us-west4.rep.googleapis.com/",
 "location": "us-west4"
+},
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://spanner.us-west8.rep.googleapis.com/",
+"location": "us-west8"
 }
 ],
 "fullyEncodeReservedExpansion": true,
@@ -3284,7 +3304,7 @@
 }
 }
 },
-"revision": "20240918",
+"revision": "20240930",
 "rootUrl": "https://spanner.googleapis.com/",
 "schemas": {
 "AutoscalingConfig": {

googleapiclient/discovery_cache/documents/speech.v1.json

@@ -524,7 +524,7 @@
 }
 }
 },
-"revision": "20240625",
+"revision": "20240926",
 "rootUrl": "https://speech.googleapis.com/",
 "schemas": {
 "ABNFGrammar": {
@@ -1044,7 +1044,8 @@
 "OGG_OPUS",
 "SPEEX_WITH_HEADER_BYTE",
 "MP3",
-"WEBM_OPUS"
+"WEBM_OPUS",
+"ALAW"
 ],
 "enumDescriptions": [
 "Not specified.",
@@ -1056,7 +1057,8 @@
 "Opus encoded audio frames in Ogg container ([OggOpus](https://wiki.xiph.org/OggOpus)). `sample_rate_hertz` must be one of 8000, 12000, 16000, 24000, or 48000.",
 "Although the use of lossy encodings is not recommended, if a very low bitrate encoding is required, `OGG_OPUS` is highly preferred over Speex encoding. The [Speex](https://speex.org/) encoding supported by Cloud Speech API has a header byte in each block, as in MIME type `audio/x-speex-with-header-byte`. It is a variant of the RTP Speex encoding defined in [RFC 5574](https://tools.ietf.org/html/rfc5574). The stream is a sequence of blocks, one block per RTP packet. Each block starts with a byte containing the length of the block, in bytes, followed by one or more frames of Speex data, padded to an integral number of bytes (octets) as specified in RFC 5574. In other words, each RTP header is replaced with a single byte containing the block length. Only Speex wideband is supported. `sample_rate_hertz` must be 16000.",
 "MP3 audio. MP3 encoding is a Beta feature and only available in v1p1beta1. Support all standard MP3 bitrates (which range from 32-320 kbps). When using this encoding, `sample_rate_hertz` has to match the sample rate of the file being used.",
-"Opus encoded audio frames in WebM container ([WebM](https://www.webmproject.org/docs/container/)). `sample_rate_hertz` must be one of 8000, 12000, 16000, 24000, or 48000."
+"Opus encoded audio frames in WebM container ([WebM](https://www.webmproject.org/docs/container/)). `sample_rate_hertz` must be one of 8000, 12000, 16000, 24000, or 48000.",
+"8-bit samples that compand 13-bit audio samples using G.711 PCMU/a-law."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/speech.v1p1beta1.json

@@ -524,7 +524,7 @@
 }
 }
 },
-"revision": "20240625",
+"revision": "20240926",
 "rootUrl": "https://speech.googleapis.com/",
 "schemas": {
 "ABNFGrammar": {
@@ -1060,7 +1060,8 @@
 "OGG_OPUS",
 "SPEEX_WITH_HEADER_BYTE",
 "MP3",
-"WEBM_OPUS"
+"WEBM_OPUS",
+"ALAW"
 ],
 "enumDescriptions": [
 "Not specified.",
@@ -1072,7 +1073,8 @@
 "Opus encoded audio frames in Ogg container ([OggOpus](https://wiki.xiph.org/OggOpus)). `sample_rate_hertz` must be one of 8000, 12000, 16000, 24000, or 48000.",
 "Although the use of lossy encodings is not recommended, if a very low bitrate encoding is required, `OGG_OPUS` is highly preferred over Speex encoding. The [Speex](https://speex.org/) encoding supported by Cloud Speech API has a header byte in each block, as in MIME type `audio/x-speex-with-header-byte`. It is a variant of the RTP Speex encoding defined in [RFC 5574](https://tools.ietf.org/html/rfc5574). The stream is a sequence of blocks, one block per RTP packet. Each block starts with a byte containing the length of the block, in bytes, followed by one or more frames of Speex data, padded to an integral number of bytes (octets) as specified in RFC 5574. In other words, each RTP header is replaced with a single byte containing the block length. Only Speex wideband is supported. `sample_rate_hertz` must be 16000.",
 "MP3 audio. MP3 encoding is a Beta feature and only available in v1p1beta1. Support all standard MP3 bitrates (which range from 32-320 kbps). When using this encoding, `sample_rate_hertz` has to match the sample rate of the file being used.",
-"Opus encoded audio frames in WebM container ([WebM](https://www.webmproject.org/docs/container/)). `sample_rate_hertz` must be one of 8000, 12000, 16000, 24000, or 48000."
+"Opus encoded audio frames in WebM container ([WebM](https://www.webmproject.org/docs/container/)). `sample_rate_hertz` must be one of 8000, 12000, 16000, 24000, or 48000.",
+"8-bit samples that compand 13-bit audio samples using G.711 PCMU/a-law."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/sqladmin.v1.json

@@ -641,7 +641,7 @@
 ]
 },
 "RotateServerCertificate": {
-"description": "Rotates the server certificate version to one previously added with the addServerCertificate method. For instances not using Certificate Authority Service (CAS) server CA, please use RotateServerCa instead.",
+"description": "Rotates the server certificate version to one previously added with the addServerCertificate method. For instances not using Certificate Authority Service (CAS) server CA, use RotateServerCa instead.",
 "flatPath": "v1/projects/{project}/instances/{instance}/rotateServerCertificate",
 "httpMethod": "POST",
 "id": "sql.instances.RotateServerCertificate",
@@ -711,7 +711,7 @@
 ]
 },
 "addServerCa": {
-"description": "Adds a new trusted Certificate Authority (CA) version for the specified instance. Required to prepare for a certificate rotation. If a CA version was previously added but never used in a certificate rotation, this operation replaces that version. There cannot be more than one CA version waiting to be rotated in. For instances that have enabled Certificate Authority Service (CAS) based server CA, please use AddServerCertificate to add a new server certificate.",
+"description": "Adds a new trusted Certificate Authority (CA) version for the specified instance. Required to prepare for a certificate rotation. If a CA version was previously added but never used in a certificate rotation, this operation replaces that version. There cannot be more than one CA version waiting to be rotated in. For instances that have enabled Certificate Authority Service (CAS) based server CA, use AddServerCertificate to add a new server certificate.",
 "flatPath": "v1/projects/{project}/instances/{instance}/addServerCa",
 "httpMethod": "POST",
 "id": "sql.instances.addServerCa",
@@ -743,7 +743,7 @@
 ]
 },
 "addServerCertificate": {
-"description": "Add a new trusted server certificate version for the specified instance using Certificate Authority Service (CAS) server CA. Required to prepare for a certificate rotation. If a server certificate version was previously added but never used in a certificate rotation, this operation replaces that version. There cannot be more than one certificate version waiting to be rotated in. For instances not using CAS server CA, please use AddServerCa instead.",
+"description": "Add a new trusted server certificate version for the specified instance using Certificate Authority Service (CAS) server CA. Required to prepare for a certificate rotation. If a server certificate version was previously added but never used in a certificate rotation, this operation replaces that version. There cannot be more than one certificate version waiting to be rotated in. For instances not using CAS server CA, use AddServerCa instead.",
 "flatPath": "v1/projects/{project}/instances/{instance}/addServerCertificate",
 "httpMethod": "POST",
 "id": "sql.instances.addServerCertificate",
@@ -819,28 +819,6 @@
 "instance"
 ],
 "parameters": {
-"enableFinalBackup": {
-"description": "Flag to opt-in for final backup. By default, it is turned off.",
-"location": "query",
-"type": "boolean"
-},
-"finalBackupDescription": {
-"description": "Optional. The description of the final backup.",
-"location": "query",
-"type": "string"
-},
-"finalBackupExpiryTime": {
-"description": "Optional. Final Backup expiration time. Timestamp in UTC of when this resource is considered expired.",
-"format": "google-datetime",
-"location": "query",
-"type": "string"
-},
-"finalBackupTtlDays": {
-"description": "Optional. Retention period of the final backup.",
-"format": "int64",
-"location": "query",
-"type": "string"
-},
 "instance": {
 "description": "Cloud SQL instance ID. This does not include the project ID.",
 "location": "path",
@@ -1408,7 +1386,7 @@
 ]
 },
 "rotateServerCa": {
-"description": "Rotates the server certificate to one signed by the Certificate Authority (CA) version previously added with the addServerCA method. For instances that have enabled Certificate Authority Service (CAS) based server CA, please use RotateServerCertificate to rotate the server certificate.",
+"description": "Rotates the server certificate to one signed by the Certificate Authority (CA) version previously added with the addServerCA method. For instances that have enabled Certificate Authority Service (CAS) based server CA, use RotateServerCertificate to rotate the server certificate.",
 "flatPath": "v1/projects/{project}/instances/{instance}/rotateServerCa",
 "httpMethod": "POST",
 "id": "sql.instances.rotateServerCa",
@@ -1691,11 +1669,6 @@
 "project"
 ],
 "parameters": {
-"filter": {
-"description": "Optional. A filter string that follows the rules of EBNF grammar (https://google.aip.dev/assets/misc/ebnf-filtering.txt). Cloud SQL provides filters for status, operationType, and startTime.",
-"location": "query",
-"type": "string"
-},
 "instance": {
 "description": "Cloud SQL instance ID. This does not include the project ID.",
 "location": "query",
@@ -2393,7 +2366,7 @@
 }
 }
 },
-"revision": "20240925",
+"revision": "20241004",
 "rootUrl": "https://sqladmin.googleapis.com/",
 "schemas": {
 "AclEntry": {
@@ -2583,10 +2556,6 @@
 "kind": {
 "description": "This is always `sql#backupContext`.",
 "type": "string"
-},
-"name": {
-"description": "The name of the backup. Format: projects/{project}/backups/{backup}",
-"type": "string"
 }
 },
 "type": "object"
@@ -2654,8 +2623,8 @@
 ],
 "enumDescriptions": [
 "This is an unknown BackupKind.",
-"The snapshot based backups",
-"Physical backups"
+"Snapshot-based backups.",
+"Physical backups."
 ],
 "type": "string"
 },
@@ -4628,17 +4597,9 @@ false
 "description": "Database instance restore backup request.",
 "id": "InstancesRestoreBackupRequest",
 "properties": {
-"backup": {
-"description": "The name of the backup to restore from in following format: projects/{project-id}/backups/{backup-uid} Only one of restore_backup_context or backup can be passed to the input.",
-"type": "string"
-},
 "restoreBackupContext": {
 "$ref": "RestoreBackupContext",
 "description": "Parameters required to perform the restore backup operation."
-},
-"restoreInstanceSettings": {
-"$ref": "DatabaseInstance",
-"description": "Optional. Restore instance settings overrides the instance settings stored as part of the backup. Instance's major database version cannot be changed and the disk size can only be increased. This feature is only available for restores to new instances using the backup name."
 }
 },
 "type": "object"
@@ -4719,7 +4680,7 @@ false
 "GOOGLE_MANAGED_CAS_CA"
 ],
 "enumDescriptions": [
-"CA mode is unknown.",
+"CA mode is unspecified. It is effectively the same as `GOOGLE_MANAGED_INTERNAL_CA`.",
 "Google-managed self-signed internal CA.",
 "Google-managed regional CA part of root CA hierarchy hosted on Google Cloud's Certificate Authority Service (CAS)."
 ],
@@ -5037,7 +4998,6 @@ false
 "AUTO_RESTART",
 "REENCRYPT",
 "SWITCHOVER",
-"UPDATE_BACKUP",
 "ACQUIRE_SSRS_LEASE",
 "RELEASE_SSRS_LEASE",
 "RECONFIGURE_OLD_PRIMARY",
@@ -5089,7 +5049,6 @@ false,
 false,
 false,
 false,
-false,
 true,
 true,
 false,
@@ -5135,7 +5094,6 @@ false
 "Performs auto-restart of an HA-enabled Cloud SQL database for auto recovery.",
 "Re-encrypts CMEK instances with latest key version.",
 "Switches the roles of the primary and replica pair. The target instance should be the replica.",
-"Update a backup.",
 "Acquire a lease for the setup of SQL Server Reporting Services (SSRS).",
 "Release a lease for the setup of SQL Server Reporting Services (SSRS).",
 "Reconfigures old primary after a promote replica operation. Effect of a promote operation to the old primary is executed in this operation, asynchronously from the promote replica operation executed to the replica.",
@@ -5288,13 +5246,6 @@ false
 "nextPageToken": {
 "description": "The continuation token, used to page through large result sets. Provide this value in a subsequent request to return the next page of results.",
 "type": "string"
-},
-"warnings": {
-"description": "List of warnings that occurred while handling the request.",
-"items": {
-"$ref": "ApiWarning"
-},
-"type": "array"
 }
 },
 "type": "object"
@@ -5374,6 +5325,33 @@ false
 },
 "type": "object"
 },
+"PscAutoConnectionConfig": {
+"description": "Settings for an automatically-setup Private Service Connect consumer endpoint that is used to connect to a Cloud SQL instance.",
+"id": "PscAutoConnectionConfig",
+"properties": {
+"consumerNetwork": {
+"description": "The consumer network of this consumer endpoint. This must be a resource path that includes both the host project and the network name. For example, `projects/project1/global/networks/network1`. The consumer host project of this network might be different from the consumer service project.",
+"type": "string"
+},
+"consumerNetworkStatus": {
+"description": "The connection policy status of the consumer network.",
+"type": "string"
+},
+"consumerProject": {
+"description": "This is the project ID of consumer service project of this consumer endpoint. Optional. This is only applicable if consumer_network is a shared vpc network.",
+"type": "string"
+},
+"ipAddress": {
+"description": "The IP address of the consumer endpoint.",
+"type": "string"
+},
+"status": {
+"description": "The connection status of the consumer endpoint.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "PscConfig": {
 "description": "PSC settings for a Cloud SQL instance.",
 "id": "PscConfig",
@@ -5385,6 +5363,13 @@ false
 },
 "type": "array"
 },
+"pscAutoConnections": {
+"description": "Optional. The list of settings for requested Private Service Connect consumer endpoints that can be used to connect to this Cloud SQL instance.",
+"items": {
+"$ref": "PscAutoConnectionConfig"
+},
+"type": "array"
+},
 "pscEnabled": {
 "description": "Whether PSC connectivity is enabled for this instance.",
 "type": "boolean"