google-api-python-client 2.153.0__py2.py3-none-any.whl → 2.155.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/ml.v1.json

@@ -512,7 +512,7 @@
 "operations": {
 "methods": {
 "cancel": {
-"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
+"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/operations/{operationsId}:cancel",
 "httpMethod": "POST",
 "id": "ml.projects.locations.operations.cancel",
@@ -1391,7 +1391,7 @@
 "operations": {
 "methods": {
 "cancel": {
-"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
+"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.",
 "flatPath": "v1/projects/{projectsId}/operations/{operationsId}:cancel",
 "httpMethod": "POST",
 "id": "ml.projects.operations.cancel",
@@ -1486,7 +1486,7 @@
 }
 }
 },
-"revision": "20240607",
+"revision": "20241116",
 "rootUrl": "https://ml.googleapis.com/",
 "schemas": {
 "GoogleApi__HttpBody": {

googleapiclient/discovery_cache/documents/monitoring.v3.json

@@ -1205,7 +1205,7 @@
 ],
 "parameters": {
 "filter": {
-"description": "If this field is empty, all custom and system-defined metric descriptors are returned. Otherwise, the filter (https://cloud.google.com/monitoring/api/v3/filters) specifies which metric descriptors are to be returned. For example, the following filter matches all custom metrics (https://cloud.google.com/monitoring/custom-metrics): metric.type = starts_with(\"custom.googleapis.com/\") ",
+"description": "Optional. If this field is empty, all custom and system-defined metric descriptors are returned. Otherwise, the filter (https://cloud.google.com/monitoring/api/v3/filters) specifies which metric descriptors are to be returned. For example, the following filter matches all custom metrics (https://cloud.google.com/monitoring/custom-metrics): metric.type = starts_with(\"custom.googleapis.com/\") ",
 "location": "query",
 "type": "string"
 },
@@ -1217,13 +1217,13 @@
 "type": "string"
 },
 "pageSize": {
-"description": "A positive number that is the maximum number of results to return. The default and maximum value is 10,000. If a page_size <= 0 or > 10,000 is submitted, will instead return a maximum of 10,000 results.",
+"description": "Optional. A positive number that is the maximum number of results to return. The default and maximum value is 10,000. If a page_size <= 0 or > 10,000 is submitted, will instead return a maximum of 10,000 results.",
 "format": "int32",
 "location": "query",
 "type": "integer"
 },
 "pageToken": {
-"description": "If this field is not empty then it must contain the nextPageToken value returned by a previous call to this method. Using this field causes the method to return additional results from the previous method call.",
+"description": "Optional. If this field is not empty then it must contain the nextPageToken value returned by a previous call to this method. Using this field causes the method to return additional results from the previous method call.",
 "location": "query",
 "type": "string"
 }
@@ -2715,7 +2715,7 @@
 }
 }
 },
-"revision": "20241017",
+"revision": "20241114",
 "rootUrl": "https://monitoring.googleapis.com/",
 "schemas": {
 "Aggregation": {
@@ -5263,6 +5263,10 @@
 "description": "Optional. The alerting rule name of this alert in the corresponding Prometheus configuration file.Some external tools may require this field to be populated correctly in order to refer to the original Prometheus configuration file. The rule group name and the alert name are necessary to update the relevant AlertPolicies in case the definition of the rule group changes in the future.This field is optional. If this field is not empty, then it must be a valid Prometheus label name (https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). This field may not exceed 2048 Unicode characters in length.",
 "type": "string"
 },
+"disableMetricValidation": {
+"description": "Optional. Whether to disable metric existence validation for this condition.This allows alerting policies to be defined on metrics that do not yet exist, improving advanced customer workflows such as configuring alerting policies using Terraform.Users with the monitoring.alertPolicyViewer role are able to see the name of the non-existent metric in the alerting policy condition.",
+"type": "boolean"
+},
 "duration": {
 "description": "Optional. Alerts are considered firing once their PromQL expression was evaluated to be \"true\" for this long. Alerts whose PromQL expression was not evaluated to be \"true\" for long enough are considered pending. Must be a non-negative duration or missing. This field is optional. Its default value is zero.",
 "format": "google-duration",

googleapiclient/discovery_cache/documents/mybusinessaccountmanagement.v1.json

@@ -530,7 +530,7 @@
 }
 }
 },
-"revision": "20240707",
+"revision": "20241120",
 "rootUrl": "https://mybusinessaccountmanagement.googleapis.com/",
 "schemas": {
 "AcceptInvitationRequest": {
@@ -844,18 +844,18 @@
 "type": "object"
 },
 "PostalAddress": {
-"description": "Represents a postal address, e.g. for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created via user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, please see: https://support.google.com/business/answer/6397478",
+"description": "Represents a postal address. For example for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created by user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, see: https://support.google.com/business/answer/6397478",
 "id": "PostalAddress",
 "properties": {
 "addressLines": {
-"description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (e.g. \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (e.g. Japan), address_language is used to make it explicit (e.g. \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
+"description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (For example \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (For example Japan), address_language is used to make it explicit (For example \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
 "items": {
 "type": "string"
 },
 "type": "array"
 },
 "administrativeArea": {
-"description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (e.g. \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. E.g. in Switzerland this should be left unpopulated.",
+"description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (For example \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. For example in Switzerland this should be left unpopulated.",
 "type": "string"
 },
 "languageCode": {
@@ -871,7 +871,7 @@
 "type": "string"
 },
 "postalCode": {
-"description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (e.g. state/zip validation in the U.S.A.).",
+"description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (For example state/zip validation in the U.S.A.).",
 "type": "string"
 },
 "recipients": {
@@ -891,7 +891,7 @@
 "type": "integer"
 },
 "sortingCode": {
-"description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (e.g. \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (e.g. C\u00f4te d'Ivoire).",
+"description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (For example \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (For example C\u00f4te d'Ivoire).",
 "type": "string"
 },
 "sublocality": {

googleapiclient/discovery_cache/documents/mybusinessbusinessinformation.v1.json

@@ -612,7 +612,7 @@
 }
 }
 },
-"revision": "20241002",
+"revision": "20241120",
 "rootUrl": "https://mybusinessbusinessinformation.googleapis.com/",
 "schemas": {
 "AdWordsLocationExtensions": {
@@ -1386,18 +1386,18 @@
 "type": "object"
 },
 "PostalAddress": {
-"description": "Represents a postal address, e.g. for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created via user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, please see: https://support.google.com/business/answer/6397478",
+"description": "Represents a postal address. For example for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created by user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, see: https://support.google.com/business/answer/6397478",
 "id": "PostalAddress",
 "properties": {
 "addressLines": {
-"description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (e.g. \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (e.g. Japan), address_language is used to make it explicit (e.g. \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
+"description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (For example \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (For example Japan), address_language is used to make it explicit (For example \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
 "items": {
 "type": "string"
 },
 "type": "array"
 },
 "administrativeArea": {
-"description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (e.g. \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. E.g. in Switzerland this should be left unpopulated.",
+"description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (For example \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. For example in Switzerland this should be left unpopulated.",
 "type": "string"
 },
 "languageCode": {
@@ -1413,7 +1413,7 @@
 "type": "string"
 },
 "postalCode": {
-"description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (e.g. state/zip validation in the U.S.A.).",
+"description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (For example state/zip validation in the U.S.A.).",
 "type": "string"
 },
 "recipients": {
@@ -1433,7 +1433,7 @@
 "type": "integer"
 },
 "sortingCode": {
-"description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (e.g. \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (e.g. C\u00f4te d'Ivoire).",
+"description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (For example \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (For example C\u00f4te d'Ivoire).",
 "type": "string"
 },
 "sublocality": {

googleapiclient/discovery_cache/documents/mybusinessverifications.v1.json

@@ -237,7 +237,7 @@
 }
 }
 },
-"revision": "20240707",
+"revision": "20241120",
 "rootUrl": "https://mybusinessverifications.googleapis.com/",
 "schemas": {
 "AddressVerificationData": {
@@ -370,18 +370,18 @@
 "type": "object"
 },
 "PostalAddress": {
-"description": "Represents a postal address, e.g. for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created via user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, please see: https://support.google.com/business/answer/6397478",
+"description": "Represents a postal address. For example for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created by user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, see: https://support.google.com/business/answer/6397478",
 "id": "PostalAddress",
 "properties": {
 "addressLines": {
-"description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (e.g. \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (e.g. Japan), address_language is used to make it explicit (e.g. \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
+"description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (For example \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (For example Japan), address_language is used to make it explicit (For example \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
 "items": {
 "type": "string"
 },
 "type": "array"
 },
 "administrativeArea": {
-"description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (e.g. \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. E.g. in Switzerland this should be left unpopulated.",
+"description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (For example \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. For example in Switzerland this should be left unpopulated.",
 "type": "string"
 },
 "languageCode": {
@@ -397,7 +397,7 @@
 "type": "string"
 },
 "postalCode": {
-"description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (e.g. state/zip validation in the U.S.A.).",
+"description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (For example state/zip validation in the U.S.A.).",
 "type": "string"
 },
 "recipients": {
@@ -417,7 +417,7 @@
 "type": "integer"
 },
 "sortingCode": {
-"description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (e.g. \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (e.g. C\u00f4te d'Ivoire).",
+"description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (For example \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (For example C\u00f4te d'Ivoire).",
 "type": "string"
 },
 "sublocality": {

googleapiclient/discovery_cache/documents/netapp.v1.json

@@ -1073,7 +1073,7 @@
 "operations": {
 "methods": {
 "cancel": {
-"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
+"description": "Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns `google.rpc.Code.UNIMPLEMENTED`. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of `1`, corresponding to `Code.CANCELLED`.",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/operations/{operationsId}:cancel",
 "httpMethod": "POST",
 "id": "netapp.projects.locations.operations.cancel",
@@ -1385,6 +1385,34 @@
 "scopes": [
 "https://www.googleapis.com/auth/cloud-platform"
 ]
+},
+"validateDirectoryService": {
+"description": "ValidateDirectoryService does a connectivity check for a directory service policy attached to the storage pool.",
+"flatPath": "v1/projects/{projectsId}/locations/{locationsId}/storagePools/{storagePoolsId}:validateDirectoryService",
+"httpMethod": "POST",
+"id": "netapp.projects.locations.storagePools.validateDirectoryService",
+"parameterOrder": [
+"name"
+],
+"parameters": {
+"name": {
+"description": "Required. Name of the storage pool",
+"location": "path",
+"pattern": "^projects/[^/]+/locations/[^/]+/storagePools/[^/]+$",
+"required": true,
+"type": "string"
+}
+},
+"path": "v1/{+name}:validateDirectoryService",
+"request": {
+"$ref": "ValidateDirectoryServiceRequest"
+},
+"response": {
+"$ref": "Operation"
+},
+"scopes": [
+"https://www.googleapis.com/auth/cloud-platform"
+]
 }
 }
 },
@@ -1648,6 +1676,34 @@
 "https://www.googleapis.com/auth/cloud-platform"
 ]
 },
+"establishPeering": {
+"description": "Establish replication peering.",
+"flatPath": "v1/projects/{projectsId}/locations/{locationsId}/volumes/{volumesId}/replications/{replicationsId}:establishPeering",
+"httpMethod": "POST",
+"id": "netapp.projects.locations.volumes.replications.establishPeering",
+"parameterOrder": [
+"name"
+],
+"parameters": {
+"name": {
+"description": "Required. The resource name of the replication, in the format of projects/{project_id}/locations/{location}/volumes/{volume_id}/replications/{replication_id}.",
+"location": "path",
+"pattern": "^projects/[^/]+/locations/[^/]+/volumes/[^/]+/replications/[^/]+$",
+"required": true,
+"type": "string"
+}
+},
+"path": "v1/{+name}:establishPeering",
+"request": {
+"$ref": "EstablishPeeringRequest"
+},
+"response": {
+"$ref": "Operation"
+},
+"scopes": [
+"https://www.googleapis.com/auth/cloud-platform"
+]
+},
 "get": {
 "description": "Describe a replication for a volume.",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/volumes/{volumesId}/replications/{replicationsId}",
@@ -1836,6 +1892,34 @@
 "scopes": [
 "https://www.googleapis.com/auth/cloud-platform"
 ]
+},
+"sync": {
+"description": "Syncs the replication. This will invoke one time volume data transfer from source to destination.",
+"flatPath": "v1/projects/{projectsId}/locations/{locationsId}/volumes/{volumesId}/replications/{replicationsId}:sync",
+"httpMethod": "POST",
+"id": "netapp.projects.locations.volumes.replications.sync",
+"parameterOrder": [
+"name"
+],
+"parameters": {
+"name": {
+"description": "Required. The resource name of the replication, in the format of projects/{project_id}/locations/{location}/volumes/{volume_id}/replications/{replication_id}.",
+"location": "path",
+"pattern": "^projects/[^/]+/locations/[^/]+/volumes/[^/]+/replications/[^/]+$",
+"required": true,
+"type": "string"
+}
+},
+"path": "v1/{+name}:sync",
+"request": {
+"$ref": "SyncReplicationRequest"
+},
+"response": {
+"$ref": "Operation"
+},
+"scopes": [
+"https://www.googleapis.com/auth/cloud-platform"
+]
 }
 }
 },
@@ -2013,7 +2097,7 @@
 }
 }
 },
-"revision": "20241021",
+"revision": "20241203",
 "rootUrl": "https://netapp.googleapis.com/",
 "schemas": {
 "ActiveDirectory": {
@@ -2428,6 +2512,10 @@
 "description": "Required. Existing destination StoragePool name.",
 "type": "string"
 },
+"tieringPolicy": {
+"$ref": "TieringPolicy",
+"description": "Optional. Tiering policy for the volume."
+},
 "volumeId": {
 "description": "Desired destination volume resource id. If not specified, source volume's resource id will be used. This value must start with a lowercase letter followed by up to 62 lowercase letters, numbers, or hyphens, and cannot end with a hyphen.",
 "type": "string"
@@ -2441,6 +2529,32 @@
 "properties": {},
 "type": "object"
 },
+"EstablishPeeringRequest": {
+"description": "EstablishPeeringRequest establishes cluster and svm peerings between the source and the destination replications.",
+"id": "EstablishPeeringRequest",
+"properties": {
+"peerClusterName": {
+"description": "Required. Name of the user's local source cluster to be peered with the destination cluster.",
+"type": "string"
+},
+"peerIpAddresses": {
+"description": "Optional. List of IPv4 ip addresses to be used for peering.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
+"peerSvmName": {
+"description": "Required. Name of the user's local source vserver svm to be peered with the destination vserver svm.",
+"type": "string"
+},
+"peerVolumeName": {
+"description": "Required. Name of the user's local source volume to be peered with the destination volume.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "ExportPolicy": {
 "description": "Defines the export policy for the volume.",
 "id": "ExportPolicy",
@@ -2478,6 +2592,75 @@
 },
 "type": "object"
 },
+"HybridPeeringDetails": {
+"description": "HybridPeeringDetails contains details about the hybrid peering.",
+"id": "HybridPeeringDetails",
+"properties": {
+"command": {
+"description": "Optional. Copy-paste-able commands to be used on user's ONTAP to accept peering requests.",
+"type": "string"
+},
+"commandExpiryTime": {
+"description": "Optional. Expiration time for the peering command to be executed on user's ONTAP.",
+"format": "google-datetime",
+"type": "string"
+},
+"passphrase": {
+"description": "Optional. Temporary passphrase generated to accept cluster peering command.",
+"type": "string"
+},
+"subnetIp": {
+"description": "Optional. IP address of the subnet.",
+"type": "string"
+}
+},
+"type": "object"
+},
+"HybridReplicationParameters": {
+"description": "The Hybrid Replication parameters for the volume.",
+"id": "HybridReplicationParameters",
+"properties": {
+"clusterLocation": {
+"description": "Optional. Name of source cluster location associated with the Hybrid replication. This is a free-form field for the display purpose only.",
+"type": "string"
+},
+"description": {
+"description": "Optional. Description of the replication.",
+"type": "string"
+},
+"labels": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Optional. Labels to be added to the replication as the key value pairs.",
+"type": "object"
+},
+"peerClusterName": {
+"description": "Required. Name of the user's local source cluster to be peered with the destination cluster.",
+"type": "string"
+},
+"peerIpAddresses": {
+"description": "Required. List of node ip addresses to be peered with.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
+"peerSvmName": {
+"description": "Required. Name of the user's local source vserver svm to be peered with the destination vserver svm.",
+"type": "string"
+},
+"peerVolumeName": {
+"description": "Required. Name of the user's local source volume to be peered with the destination volume.",
+"type": "string"
+},
+"replication": {
+"description": "Required. Desired name for the replication of this volume.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "KmsConfig": {
 "description": "KmsConfig is the customer managed encryption key(CMEK) configuration.",
 "id": "KmsConfig",
@@ -3026,6 +3209,10 @@
 "description": "Replication is a nested resource under Volume, that describes a cross-region replication relationship between 2 volumes in different regions.",
 "id": "Replication",
 "properties": {
+"clusterLocation": {
+"description": "Optional. Location of the user cluster.",
+"type": "string"
+},
 "createTime": {
 "description": "Output only. Replication create time.",
 "format": "google-datetime",
@@ -3050,6 +3237,26 @@
 "readOnly": true,
 "type": "boolean"
 },
+"hybridPeeringDetails": {
+"$ref": "HybridPeeringDetails",
+"description": "Output only. Hybrid peering details.",
+"readOnly": true
+},
+"hybridReplicationType": {
+"description": "Output only. Type of the hybrid replication.",
+"enum": [
+"HYBRID_REPLICATION_TYPE_UNSPECIFIED",
+"MIGRATION",
+"CONTINUOUS_REPLICATION"
+],
+"enumDescriptions": [
+"Unspecified hybrid replication type.",
+"Hybrid replication type for migration.",
+"Hybrid replication type for continuous replication."
+],
+"readOnly": true,
+"type": "string"
+},
 "labels": {
 "additionalProperties": {
 "type": "string"
@@ -3064,14 +3271,18 @@
 "PREPARING",
 "MIRRORED",
 "STOPPED",
-"TRANSFERRING"
+"TRANSFERRING",
+"BASELINE_TRANSFERRING",
+"ABORTED"
 ],
 "enumDescriptions": [
 "Unspecified MirrorState",
 "Destination volume is being prepared.",
 "Destination volume has been initialized and is ready to receive replication transfers.",
 "Destination volume is not receiving replication transfers.",
-"Incremental replication is in progress."
+"Incremental replication is in progress.",
+"Baseline replication is in progress.",
+"Replication is aborted."
 ],
 "readOnly": true,
 "type": "string"
@@ -3124,7 +3335,9 @@
 "READY",
 "UPDATING",
 "DELETING",
-"ERROR"
+"ERROR",
+"PENDING_CLUSTER_PEERING",
+"PENDING_SVM_PEERING"
 ],
 "enumDescriptions": [
 "Unspecified replication State",
@@ -3132,7 +3345,9 @@
 "Replication is ready.",
 "Replication is updating.",
 "Replication is deleting.",
-"Replication is in error state."
+"Replication is in error state.",
+"Replication is waiting for cluster peering to be established.",
+"Replication is waiting for SVM peering to be established."
 ],
 "readOnly": true,
 "type": "string"
@@ -3529,6 +3744,12 @@
 "properties": {},
 "type": "object"
 },
+"SyncReplicationRequest": {
+"description": "SyncReplicationRequest syncs the replication from source to destination.",
+"id": "SyncReplicationRequest",
+"properties": {},
+"type": "object"
+},
 "TieringPolicy": {
 "description": "Defines tiering policy for the volume.",
 "id": "TieringPolicy",
@@ -3601,6 +3822,25 @@
 },
 "type": "object"
 },
+"ValidateDirectoryServiceRequest": {
+"description": "ValidateDirectoryServiceRequest validates the directory service policy attached to the storage pool.",
+"id": "ValidateDirectoryServiceRequest",
+"properties": {
+"directoryServiceType": {
+"description": "Type of directory service policy attached to the storage pool.",
+"enum": [
+"DIRECTORY_SERVICE_TYPE_UNSPECIFIED",
+"ACTIVE_DIRECTORY"
+],
+"enumDescriptions": [
+"Directory service type is not specified.",
+"Active directory policy attached to the storage pool."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "VerifyKmsConfigRequest": {
 "description": "VerifyKmsConfigRequest specifies the KMS config to be validated.",
 "id": "VerifyKmsConfigRequest",
@@ -3687,6 +3927,10 @@
 "readOnly": true,
 "type": "boolean"
 },
+"hybridReplicationParameters": {
+"$ref": "HybridReplicationParameters",
+"description": "Optional. The Hybrid Replication parameters for the volume."
+},
 "kerberosEnabled": {
 "description": "Optional. Flag indicating if the volume is a kerberos volume or not, export policy rules control kerberos security modes (krb5, krb5i, krb5p).",
 "type": "boolean"
@@ -3872,7 +4116,9 @@
 "UPDATING",
 "RESTORING",
 "DISABLED",
-"ERROR"
+"ERROR",
+"PREPARING",
+"READ_ONLY"
 ],
 "enumDescriptions": [
 "Unspecified Volume State",
@@ -3882,7 +4128,9 @@
 "Volume State is Updating",
 "Volume State is Restoring",
 "Volume State is Disabled",
-"Volume State is Error"
+"Volume State is Error",
+"Volume State is Preparing. Note that this is different from CREATING where CREATING means the volume is being created, while PREPARING means the volume is created and now being prepared for the replication.",
+"Volume State is Read Only"
 ],
 "readOnly": true,
 "type": "string"