google-api-python-client 2.165.0__py2.py3-none-any.whl → 2.167.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/metastore.v1beta.json

@@ -143,6 +143,12 @@
 "name"
 ],
 "parameters": {
+"extraLocationTypes": {
+"description": "Optional. A list of extra location types that should be used as conditions for controlling the visibility of the locations.",
+"location": "query",
+"repeated": true,
+"type": "string"
+},
 "filter": {
 "description": "A filter to narrow down results to a preferred subset. The filtering language accepts strings like \"displayName=tokyo\", and is documented in more detail in AIP-160 (https://google.aip.dev/160).",
 "location": "query",
@@ -1796,7 +1802,7 @@
 }
 }
 },
-"revision": "20250227",
+"revision": "20250324",
 "rootUrl": "https://metastore.googleapis.com/",
 "schemas": {
 "AlterMetadataResourceLocationRequest": {

googleapiclient/discovery_cache/documents/migrationcenter.v1.json

@@ -168,6 +168,12 @@
 "name"
 ],
 "parameters": {
+"extraLocationTypes": {
+"description": "Optional. A list of extra location types that should be used as conditions for controlling the visibility of the locations.",
+"location": "query",
+"repeated": true,
+"type": "string"
+},
 "filter": {
 "description": "A filter to narrow down results to a preferred subset. The filtering language accepts strings like `\"displayName=tokyo\"`, and is documented in more detail in [AIP-160](https://google.aip.dev/160).",
 "location": "query",
@@ -2396,7 +2402,7 @@
 }
 }
 },
-"revision": "20250227",
+"revision": "20250320",
 "rootUrl": "https://migrationcenter.googleapis.com/",
 "schemas": {
 "AddAssetsToGroupRequest": {

googleapiclient/discovery_cache/documents/migrationcenter.v1alpha1.json

@@ -168,6 +168,12 @@
 "name"
 ],
 "parameters": {
+"extraLocationTypes": {
+"description": "Optional. A list of extra location types that should be used as conditions for controlling the visibility of the locations.",
+"location": "query",
+"repeated": true,
+"type": "string"
+},
 "filter": {
 "description": "A filter to narrow down results to a preferred subset. The filtering language accepts strings like `\"displayName=tokyo\"`, and is documented in more detail in [AIP-160](https://google.aip.dev/160).",
 "location": "query",
@@ -1831,7 +1837,7 @@
 ],
 "parameters": {
 "name": {
-"description": "Output only. Name of the preference set.",
+"description": "Output only. Name of the PreferenceSet.",
 "location": "path",
 "pattern": "^projects/[^/]+/locations/[^/]+/preferenceSets/[^/]+$",
 "required": true,
@@ -2548,7 +2554,7 @@
 }
 }
 },
-"revision": "20250220",
+"revision": "20250320",
 "rootUrl": "https://migrationcenter.googleapis.com/",
 "schemas": {
 "AddAssetsToGroupRequest": {
@@ -7100,7 +7106,7 @@ false
 "type": "string"
 },
 "name": {
-"description": "Output only. Name of the preference set.",
+"description": "Output only. Name of the PreferenceSet.",
 "readOnly": true,
 "type": "string"
 },

googleapiclient/discovery_cache/documents/monitoring.v1.json

@@ -753,7 +753,7 @@
 }
 }
 },
-"revision": "20250227",
+"revision": "20250329",
 "rootUrl": "https://monitoring.googleapis.com/",
 "schemas": {
 "Aggregation": {
@@ -1448,7 +1448,9 @@
 "UPTIME_CHECK_FAILURE",
 "CLOUD_ALERTING_ALERT",
 "SERVICE_HEALTH_INCIDENT",
-"SAP_BACKINT"
+"SAP_BACKINT",
+"SAP_AVAILABILITY",
+"SAP_OPERATIONS"
 ],
 "enumDescriptions": [
 "No event type specified.",
@@ -1473,7 +1475,9 @@
 "Failure of a Cloud Monitoring uptime check.",
 "Alerts from Cloud Alerting",
 "Incidents from Service Health",
-"Agent for SAP Backint related events."
+"Agent for SAP Backint related events.",
+"Agent for SAP availability related events.",
+"Agent for SAP operations related events."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/monitoring.v3.json

@@ -2720,7 +2720,7 @@
 }
 }
 },
-"revision": "20250227",
+"revision": "20250323",
 "rootUrl": "https://monitoring.googleapis.com/",
 "schemas": {
 "Aggregation": {
@@ -4423,6 +4423,13 @@
 "unit": {
 "description": "The unit in which all time_series point values are reported. unit follows the UCUM format for units as seen in https://unitsofmeasure.org/ucum.html. If different time_series have different units (for example, because they come from different metric types, or a unit is absent), then unit will be \"{not_a_unit}\".",
 "type": "string"
+},
+"unreachable": {
+"description": "Cloud regions that were unreachable which may have caused incomplete data to be returned.",
+"items": {
+"type": "string"
+},
+"type": "array"
 }
 },
 "type": "object"
@@ -6097,6 +6104,10 @@
 },
 "type": "array"
 },
+"disabled": {
+"description": "Whether the check is disabled or not.",
+"type": "boolean"
+},
 "displayName": {
 "description": "A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.",
 "type": "string"

googleapiclient/discovery_cache/documents/mybusinessaccountmanagement.v1.json

@@ -530,7 +530,7 @@
 }
 }
 },
-"revision": "20241120",
+"revision": "20250319",
 "rootUrl": "https://mybusinessaccountmanagement.googleapis.com/",
 "schemas": {
 "AcceptInvitationRequest": {
@@ -844,18 +844,18 @@
 "type": "object"
 },
 "PostalAddress": {
-"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",
+"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 or 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 (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).",
+"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 or 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). In 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 (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.",
+"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. 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": {
@@ -863,7 +863,7 @@
 "type": "string"
 },
 "locality": {
-"description": "Optional. Generally refers to the city/town portion of the address. Examples: US city, IT comune, UK post town. In regions of the world where localities are not well defined or do not fit into this structure well, leave locality empty and use address_lines.",
+"description": "Optional. Generally refers to the city or town portion of the address. Examples: US city, IT comune, UK post town. In regions of the world where localities are not well defined or do not fit into this structure well, leave `locality` empty and use `address_lines`.",
 "type": "string"
 },
 "organization": {
@@ -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 (For example 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 or zip code validation in the United States).",
 "type": "string"
 },
 "recipients": {
@@ -891,11 +891,11 @@
 "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 (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).",
+"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\" (C\u00f4te d'Ivoire).",
 "type": "string"
 },
 "sublocality": {
-"description": "Optional. Sublocality of the address. For example, this can be neighborhoods, boroughs, districts.",
+"description": "Optional. Sublocality of the address. For example, this can be a neighborhood, borough, or district.",
 "type": "string"
 }
 },

googleapiclient/discovery_cache/documents/mybusinessbusinessinformation.v1.json

@@ -612,7 +612,7 @@
 }
 }
 },
-"revision": "20250217",
+"revision": "20250319",
 "rootUrl": "https://mybusinessbusinessinformation.googleapis.com/",
 "schemas": {
 "AdWordsLocationExtensions": {
@@ -1387,18 +1387,18 @@
 "type": "object"
 },
 "PostalAddress": {
-"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",
+"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 or 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 (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).",
+"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 or 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). In 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 (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.",
+"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. 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": {
@@ -1406,7 +1406,7 @@
 "type": "string"
 },
 "locality": {
-"description": "Optional. Generally refers to the city/town portion of the address. Examples: US city, IT comune, UK post town. In regions of the world where localities are not well defined or do not fit into this structure well, leave locality empty and use address_lines.",
+"description": "Optional. Generally refers to the city or town portion of the address. Examples: US city, IT comune, UK post town. In regions of the world where localities are not well defined or do not fit into this structure well, leave `locality` empty and use `address_lines`.",
 "type": "string"
 },
 "organization": {
@@ -1414,7 +1414,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 (For example 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 or zip code validation in the United States).",
 "type": "string"
 },
 "recipients": {
@@ -1434,11 +1434,11 @@
 "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 (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).",
+"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\" (C\u00f4te d'Ivoire).",
 "type": "string"
 },
 "sublocality": {
-"description": "Optional. Sublocality of the address. For example, this can be neighborhoods, boroughs, districts.",
+"description": "Optional. Sublocality of the address. For example, this can be a neighborhood, borough, or district.",
 "type": "string"
 }
 },

googleapiclient/discovery_cache/documents/mybusinessverifications.v1.json

@@ -237,7 +237,7 @@
 }
 }
 },
-"revision": "20241120",
+"revision": "20250319",
 "rootUrl": "https://mybusinessverifications.googleapis.com/",
 "schemas": {
 "AddressVerificationData": {
@@ -370,18 +370,18 @@
 "type": "object"
 },
 "PostalAddress": {
-"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",
+"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 or 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 (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).",
+"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 or 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). In 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 (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.",
+"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. 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": {
@@ -389,7 +389,7 @@
 "type": "string"
 },
 "locality": {
-"description": "Optional. Generally refers to the city/town portion of the address. Examples: US city, IT comune, UK post town. In regions of the world where localities are not well defined or do not fit into this structure well, leave locality empty and use address_lines.",
+"description": "Optional. Generally refers to the city or town portion of the address. Examples: US city, IT comune, UK post town. In regions of the world where localities are not well defined or do not fit into this structure well, leave `locality` empty and use `address_lines`.",
 "type": "string"
 },
 "organization": {
@@ -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 (For example 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 or zip code validation in the United States).",
 "type": "string"
 },
 "recipients": {
@@ -417,11 +417,11 @@
 "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 (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).",
+"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\" (C\u00f4te d'Ivoire).",
 "type": "string"
 },
 "sublocality": {
-"description": "Optional. Sublocality of the address. For example, this can be neighborhoods, boroughs, districts.",
+"description": "Optional. Sublocality of the address. For example, this can be a neighborhood, borough, or district.",
 "type": "string"
 }
 },

googleapiclient/discovery_cache/documents/netapp.v1.json

@@ -2264,7 +2264,7 @@
 }
 }
 },
-"revision": "20250129",
+"revision": "20250312",
 "rootUrl": "https://netapp.googleapis.com/",
 "schemas": {
 "ActiveDirectory": {
@@ -4083,7 +4083,7 @@
 "id": "TieringPolicy",
 "properties": {
 "coolingThresholdDays": {
-"description": "Optional. Time in days to mark the volume's data block as cold and make it eligible for tiering, can be range from 7-183. Default is 31.",
+"description": "Optional. Time in days to mark the volume's data block as cold and make it eligible for tiering, can be range from 2-183. Default is 31.",
 "format": "int32",
 "type": "integer"
 },

googleapiclient/discovery_cache/documents/netapp.v1beta1.json

@@ -2264,7 +2264,7 @@
 }
 }
 },
-"revision": "20250129",
+"revision": "20250312",
 "rootUrl": "https://netapp.googleapis.com/",
 "schemas": {
 "ActiveDirectory": {
@@ -3934,6 +3934,10 @@
 "readOnly": true,
 "type": "string"
 },
+"customPerformanceEnabled": {
+"description": "Optional. True if using Independent Scaling of capacity and performance (Hyperdisk) By default set to false",
+"type": "boolean"
+},
 "description": {
 "description": "Optional. Description of the storage pool",
 "type": "string"
@@ -4047,6 +4051,16 @@
 "readOnly": true,
 "type": "string"
 },
+"totalIops": {
+"description": "Optional. Custom Performance Total IOPS of the pool If not provided, it will be calculated based on the total_throughput_mibps",
+"format": "int64",
+"type": "string"
+},
+"totalThroughputMibps": {
+"description": "Optional. Custom Performance Total Throughput of the pool (in MiB/s)",
+"format": "int64",
+"type": "string"
+},
 "volumeCapacityGib": {
 "description": "Output only. Allocated size of all volumes in GIB in the storage pool",
 "format": "int64",
@@ -4083,7 +4097,7 @@
 "id": "TieringPolicy",
 "properties": {
 "coolingThresholdDays": {
-"description": "Optional. Time in days to mark the volume's data block as cold and make it eligible for tiering, can be range from 7-183. Default is 31.",
+"description": "Optional. Time in days to mark the volume's data block as cold and make it eligible for tiering, can be range from 2-183. Default is 31.",
 "format": "int32",
 "type": "integer"
 },

googleapiclient/discovery_cache/documents/networkconnectivity.v1.json

@@ -2919,7 +2919,7 @@
 }
 }
 },
-"revision": "20250305",
+"revision": "20250318",
 "rootUrl": "https://networkconnectivity.googleapis.com/",
 "schemas": {
 "AcceptHubSpokeRequest": {
@@ -3649,6 +3649,17 @@
 "description": "A description of this resource.",
 "type": "string"
 },
+"excludeCidrRanges": {
+"description": "Optional. ExcludeCidrRanges flag. Specifies a set of CIDR blocks that allows exclusion of particular CIDR ranges from the auto-allocation process, without having to reserve these blocks",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
+"immutable": {
+"description": "Optional. Immutable ranges cannot have their fields modified, except for labels and description.",
+"type": "boolean"
+},
 "ipCidrRange": {
 "description": "The IP range that this internal range defines. NOTE: IPv6 ranges are limited to usage=EXTERNAL_TO_VPC and peering=FOR_SELF. NOTE: For IPv6 Ranges this field is compulsory, i.e. the address range must be specified explicitly.",
 "type": "string"
@@ -3809,6 +3820,14 @@
 "readOnly": true,
 "type": "string"
 },
+"proposedExcludeExportRanges": {
+"description": "Output only. The proposed exclude export IP ranges waiting for hub administration's approval.",
+"items": {
+"type": "string"
+},
+"readOnly": true,
+"type": "array"
+},
 "proposedIncludeExportRanges": {
 "description": "Optional. The proposed include export IP ranges waiting for hub administration's approval.",
 "items": {
@@ -3880,6 +3899,14 @@
 "readOnly": true,
 "type": "array"
 },
+"proposedExcludeExportRanges": {
+"description": "Output only. The proposed exclude export IP ranges waiting for hub administration's approval.",
+"items": {
+"type": "string"
+},
+"readOnly": true,
+"type": "array"
+},
 "proposedIncludeExportRanges": {
 "description": "Optional. The proposed include export IP ranges waiting for hub administration's approval.",
 "items": {

googleapiclient/discovery_cache/documents/networkconnectivity.v1alpha1.json

@@ -1116,7 +1116,7 @@
 }
 }
 },
-"revision": "20250219",
+"revision": "20250318",
 "rootUrl": "https://networkconnectivity.googleapis.com/",
 "schemas": {
 "AuditConfig": {
@@ -1384,6 +1384,13 @@
 "description": "A description of this resource.",
 "type": "string"
 },
+"excludeCidrRanges": {
+"description": "Optional. ExcludeCidrRanges flag. Specifies a set of CIDR blocks that allows exclusion of particular CIDR ranges from the auto-allocation process, without having to reserve these blocks",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
 "immutable": {
 "description": "Optional. Immutable ranges cannot have their fields modified, except for labels and description.",
 "type": "boolean"

googleapiclient/discovery_cache/documents/networkmanagement.v1.json

@@ -758,7 +758,7 @@
 }
 }
 },
-"revision": "20250305",
+"revision": "20250319",
 "rootUrl": "https://networkmanagement.googleapis.com/",
 "schemas": {
 "AbortInfo": {
@@ -1119,7 +1119,7 @@ false
 "id": "ConnectivityTest",
 "properties": {
 "bypassFirewallChecks": {
-"description": "Whether the test should skip firewall checking. If not provided, we assume false.",
+"description": "Whether the analysis should skip firewall checking. Default value is false.",
 "type": "boolean"
 },
 "createTime": {
@@ -1134,7 +1134,7 @@ false
 },
 "destination": {
 "$ref": "Endpoint",
-"description": "Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don't intend to test."
+"description": "Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, URI of a supported endpoint, project ID, or VPC network to identify the destination location. Reachability analysis proceeds even if the destination location is ambiguous. However, the test result might include endpoints or use a destination that you don't intend to test."
 },
 "displayName": {
 "description": "Output only. The display name of a Connectivity Test.",
@@ -1184,7 +1184,7 @@ false
 },
 "source": {
 "$ref": "Endpoint",
-"description": "Required. Source specification of the Connectivity Test. You can use a combination of source IP address, virtual machine (VM) instance, or Compute Engine network to uniquely identify the source location. Examples: If the source IP address is an internal IP address within a Google Cloud Virtual Private Cloud (VPC) network, then you must also specify the VPC network. Otherwise, specify the VM instance, which already contains its internal IP address and VPC network information. If the source of the test is within an on-premises network, then you must provide the destination VPC network. If the source endpoint is a Compute Engine VM instance with multiple network interfaces, the instance itself is not sufficient to identify the endpoint. So, you must also specify the source IP address or VPC network. A reachability analysis proceeds even if the source location is ambiguous. However, the test result may include endpoints that you don't intend to test."
+"description": "Required. Source specification of the Connectivity Test. You can use a combination of source IP address, URI of a supported endpoint, project ID, or VPC network to identify the source location. Reachability analysis might proceed even if the source location is ambiguous. However, the test result might include endpoints or use a source that you don't intend to test."
 },
 "updateTime": {
 "description": "Output only. The time the test's configuration was updated.",
@@ -1513,22 +1513,22 @@ false
 "properties": {
 "appEngineVersion": {
 "$ref": "AppEngineVersionEndpoint",
-"description": "An [App Engine](https://cloud.google.com/appengine) [service version](https://cloud.google.com/appengine/docs/admin-api/reference/rest/v1/apps.services.versions)."
+"description": "An [App Engine](https://cloud.google.com/appengine) [service version](https://cloud.google.com/appengine/docs/admin-api/reference/rest/v1/apps.services.versions). Applicable only to source endpoint."
 },
 "cloudFunction": {
 "$ref": "CloudFunctionEndpoint",
-"description": "A [Cloud Function](https://cloud.google.com/functions)."
+"description": "A [Cloud Function](https://cloud.google.com/functions). Applicable only to source endpoint."
 },
 "cloudRunRevision": {
 "$ref": "CloudRunRevisionEndpoint",
-"description": "A [Cloud Run](https://cloud.google.com/run) [revision](https://cloud.google.com/run/docs/reference/rest/v1/namespaces.revisions/get)"
+"description": "A [Cloud Run](https://cloud.google.com/run) [revision](https://cloud.google.com/run/docs/reference/rest/v1/namespaces.revisions/get) Applicable only to source endpoint."
 },
 "cloudSqlInstance": {
 "description": "A [Cloud SQL](https://cloud.google.com/sql) instance URI.",
 "type": "string"
 },
 "forwardingRule": {
-"description": "A forwarding rule and its corresponding IP address represent the frontend configuration of a Google Cloud load balancer. Forwarding rules are also used for protocol forwarding, Private Service Connect and other network services to provide forwarding information in the control plane. Format: projects/{project}/global/forwardingRules/{id} or projects/{project}/regions/{region}/forwardingRules/{id}",
+"description": "A forwarding rule and its corresponding IP address represent the frontend configuration of a Google Cloud load balancer. Forwarding rules are also used for protocol forwarding, Private Service Connect and other network services to provide forwarding information in the control plane. Applicable only to destination endpoint. Format: projects/{project}/global/forwardingRules/{id} or projects/{project}/regions/{region}/forwardingRules/{id}",
 "type": "string"
 },
 "forwardingRuleTarget": {
@@ -1603,7 +1603,7 @@ false
 "type": "string"
 },
 "network": {
-"description": "A Compute Engine network URI.",
+"description": "A VPC network URI.",
 "type": "string"
 },
 "networkType": {
@@ -1616,7 +1616,7 @@ false
 "enumDescriptions": [
 "Default type if unspecified.",
 "A network hosted within Google Cloud. To receive more detailed output, specify the URI for the source or destination network.",
-"A network hosted outside of Google Cloud. This can be an on-premises network, or a network hosted by another cloud provider."
+"A network hosted outside of Google Cloud. This can be an on-premises network, an internet resource or a network hosted by another cloud provider."
 ],
 "type": "string"
 },
@@ -1626,15 +1626,15 @@ false
 "type": "integer"
 },
 "projectId": {
-"description": "Project ID where the endpoint is located. The Project ID can be derived from the URI if you provide a VM instance or network URI. The following are two cases where you must provide the project ID: 1. Only the IP address is specified, and the IP address is within a Google Cloud project. 2. When you are using Shared VPC and the IP address that you provide is from the service project. In this case, the network that the IP address resides in is defined in the host project.",
+"description": "Project ID where the endpoint is located. The project ID can be derived from the URI if you provide a endpoint or network URI. The following are two cases where you may need to provide the project ID: 1. Only the IP address is specified, and the IP address is within a Google Cloud project. 2. When you are using Shared VPC and the IP address that you provide is from the service project. In this case, the network that the IP address resides in is defined in the host project.",
 "type": "string"
 },
 "redisCluster": {
-"description": "A [Redis Cluster](https://cloud.google.com/memorystore/docs/cluster) URI.",
+"description": "A [Redis Cluster](https://cloud.google.com/memorystore/docs/cluster) URI. Applicable only to destination endpoint.",
 "type": "string"
 },
 "redisInstance": {
-"description": "A [Redis Instance](https://cloud.google.com/memorystore/docs/redis) URI.",
+"description": "A [Redis Instance](https://cloud.google.com/memorystore/docs/redis) URI. Applicable only to destination endpoint.",
 "type": "string"
 }
 },