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

googleapiclient/discovery_cache/documents/merchantapi.accounts_v1beta.json

@@ -1476,7 +1476,7 @@
 }
 }
 },
-"revision": "20250311",
+"revision": "20250319",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Accepted": {
@@ -2651,7 +2651,7 @@ false
 },
 "policy": {
 "$ref": "Policy",
-"description": "The return policy."
+"description": "Optional. The return policy."
 },
 "processRefundDays": {
 "description": "The field specifies the number of days it takes for merchants to process refunds, field is optional.",
@@ -2660,7 +2660,7 @@ false
 },
 "restockingFee": {
 "$ref": "RestockingFee",
-"description": "The restocking fee that applies to all return reason categories. This would be treated as a free restocking fee if the value is not set."
+"description": "Optional. The restocking fee that applies to all return reason categories. This would be treated as a free restocking fee if the value is not set."
 },
 "returnMethods": {
 "description": "Optional. The return methods of how customers can return an item. This value is required to not be empty unless the type of return policy is noReturns.",
@@ -2752,18 +2752,18 @@ false
 "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": {
@@ -2771,7 +2771,7 @@ false
 "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": {
@@ -2779,7 +2779,7 @@ false
 "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": {
@@ -2799,11 +2799,11 @@ false
 "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/merchantapi.products_v1beta.json

@@ -171,6 +171,45 @@
 "scopes": [
 "https://www.googleapis.com/auth/content"
 ]
+},
+"patch": {
+"description": "Updates the existing product input in your Merchant Center account. After inserting, updating, or deleting a product input, it may take several minutes before the processed product can be retrieved.",
+"flatPath": "products/v1beta/accounts/{accountsId}/productInputs/{productInputsId}",
+"httpMethod": "PATCH",
+"id": "merchantapi.accounts.productInputs.patch",
+"parameterOrder": [
+"name"
+],
+"parameters": {
+"dataSource": {
+"description": "Required. The primary or supplemental product data source where `data_source` name identifies the product input to be updated. Only API data sources are supported. Format: `accounts/{account}/dataSources/{datasource}`.",
+"location": "query",
+"type": "string"
+},
+"name": {
+"description": "Identifier. The name of the product input. Format: `\"{productinput.name=accounts/{account}/productInputs/{productinput}}\"` where the last section `productinput` consists of 4 parts: channel~content_language~feed_label~offer_id example for product input name is \"accounts/123/productInputs/online~en~US~sku123\"",
+"location": "path",
+"pattern": "^accounts/[^/]+/productInputs/[^/]+$",
+"required": true,
+"type": "string"
+},
+"updateMask": {
+"description": "Optional. The list of product attributes to be updated. If the update mask is omitted, then it is treated as implied field mask equivalent to all fields that are populated (have a non-empty value). Attributes specified in the update mask without a value specified in the body will be deleted from the product. Update mask can only be specified for top level fields in attributes and custom attributes. To specify the update mask for custom attributes you need to add the `custom_attribute.` prefix. Providing special \"*\" value for full product replacement is not supported.",
+"format": "google-fieldmask",
+"location": "query",
+"type": "string"
+}
+},
+"path": "products/v1beta/{+name}",
+"request": {
+"$ref": "ProductInput"
+},
+"response": {
+"$ref": "ProductInput"
+},
+"scopes": [
+"https://www.googleapis.com/auth/content"
+]
 }
 }
 },
@@ -242,7 +281,7 @@
 }
 }
 },
-"revision": "20250311",
+"revision": "20250317",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Attributes": {

googleapiclient/discovery_cache/documents/migrationcenter.v1alpha1.json

@@ -1831,7 +1831,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 +2548,7 @@
 }
 }
 },
-"revision": "20250220",
+"revision": "20250312",
 "rootUrl": "https://migrationcenter.googleapis.com/",
 "schemas": {
 "AddAssetsToGroupRequest": {
@@ -7100,7 +7100,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.v3.json

@@ -2720,7 +2720,7 @@
 }
 }
 },
-"revision": "20250227",
+"revision": "20250313",
 "rootUrl": "https://monitoring.googleapis.com/",
 "schemas": {
 "Aggregation": {
@@ -6097,6 +6097,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": "20250312",
 "rootUrl": "https://networkconnectivity.googleapis.com/",
 "schemas": {
 "AcceptHubSpokeRequest": {
@@ -3809,6 +3809,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 +3888,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": {