google-api-python-client 2.156.0__py2.py3-none-any.whl → 2.157.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/dlp.v2.json

@@ -230,6 +230,16 @@
 "description": "Regional Endpoint",
 "endpointUrl": "https://dlp.us-west8.rep.googleapis.com/",
 "location": "us-west8"
+},
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://dlp.us.rep.googleapis.com/",
+"location": "us"
+},
+{
+"description": "Regional Endpoint",
+"endpointUrl": "https://dlp.eu.rep.googleapis.com/",
+"location": "eu"
 }
 ],
 "fullyEncodeReservedExpansion": true,
@@ -5015,7 +5025,7 @@
 }
 }
 },
-"revision": "20241204",
+"revision": "20241215",
 "rootUrl": "https://dlp.googleapis.com/",
 "schemas": {
 "GooglePrivacyDlpV2Action": {
@@ -8243,7 +8253,7 @@
 "type": "array"
 },
 "noFilesExist": {
-"description": "True if no files exist in this cluster. If the bucket had more files than could be listed, this will be false even if no files for this cluster were seen and file_extensions_seen is empty.",
+"description": "True if no files exist in this cluster. If the file store had more files than could be listed, this will be false even if no files for this cluster were seen and file_extensions_seen is empty.",
 "type": "boolean"
 },
 "sensitivityScore": {
@@ -8391,7 +8401,7 @@
 "type": "string"
 },
 "locationType": {
-"description": "The location type of the bucket (region, dual-region, multi-region, etc). If dual-region, expect data_storage_locations to be populated.",
+"description": "The location type of the file store (region, dual-region, multi-region, etc). If dual-region, expect data_storage_locations to be populated.",
 "type": "string"
 },
 "name": {

googleapiclient/discovery_cache/documents/firebase.v1beta1.json

@@ -1324,7 +1324,7 @@
 }
 }
 },
-"revision": "20241107",
+"revision": "20241217",
 "rootUrl": "https://firebase.googleapis.com/",
 "schemas": {
 "AddFirebaseRequest": {
@@ -2162,12 +2162,12 @@
 "type": "integer"
 },
 "message": {
-"description": "Detail message",
+"description": "Detail message copybara:strip_begin(b/383363683) copybara:strip_end_and_replace optional string message = 3;",
 "type": "string"
 },
 "messageSet": {
 "$ref": "MessageSet",
-"description": "message_set associates an arbitrary proto message with the status."
+"description": "message_set associates an arbitrary proto message with the status. copybara:strip_begin(b/383363683) copybara:strip_end_and_replace optional proto2.bridge.MessageSet message_set = 5;"
 },
 "space": {
 "description": "The following are usually only present when code != 0 Space to which this status belongs",

googleapiclient/discovery_cache/documents/firebaseml.v2beta.json

@@ -206,7 +206,7 @@
 }
 }
 },
-"revision": "20241211",
+"revision": "20241217",
 "rootUrl": "https://firebaseml.googleapis.com/",
 "schemas": {
 "Date": {
@@ -1170,6 +1170,11 @@
 "description": "Optional. Text part (can be code).",
 "type": "string"
 },
+"thought": {
+"description": "Output only. Indicates if the part is thought from the model.",
+"readOnly": true,
+"type": "boolean"
+},
 "videoMetadata": {
 "$ref": "GoogleCloudAiplatformV1beta1VideoMetadata",
 "description": "Optional. Video metadata. The metadata should only be specified while the video data is presented in inline_data or file_data."

googleapiclient/discovery_cache/documents/jobs.v3.json

@@ -652,7 +652,7 @@
 }
 }
 },
-"revision": "20240620",
+"revision": "20241217",
 "rootUrl": "https://jobs.googleapis.com/",
 "schemas": {
 "ApplicationInfo": {
@@ -2313,18 +2313,18 @@ false
 "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": {
@@ -2340,7 +2340,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 (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": {
@@ -2360,7 +2360,7 @@ 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 (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": {
@@ -2597,22 +2597,22 @@ false
 "id": "TimeOfDay",
 "properties": {
 "hours": {
-"description": "Hours of day in 24 hour format. Should be from 0 to 23. An API may choose to allow the value \"24:00:00\" for scenarios like business closing time.",
+"description": "Hours of a day in 24 hour format. Must be greater than or equal to 0 and typically must be less than or equal to 23. An API may choose to allow the value \"24:00:00\" for scenarios like business closing time.",
 "format": "int32",
 "type": "integer"
 },
 "minutes": {
-"description": "Minutes of hour of day. Must be from 0 to 59.",
+"description": "Minutes of an hour. Must be greater than or equal to 0 and less than or equal to 59.",
 "format": "int32",
 "type": "integer"
 },
 "nanos": {
-"description": "Fractions of seconds in nanoseconds. Must be from 0 to 999,999,999.",
+"description": "Fractions of seconds, in nanoseconds. Must be greater than or equal to 0 and less than or equal to 999,999,999.",
 "format": "int32",
 "type": "integer"
 },
 "seconds": {
-"description": "Seconds of minutes of the time. Must normally be from 0 to 59. An API may allow the value 60 if it allows leap-seconds.",
+"description": "Seconds of a minute. Must be greater than or equal to 0 and typically must be less than or equal to 59. An API may allow the value 60 if it allows leap-seconds.",
 "format": "int32",
 "type": "integer"
 }

googleapiclient/discovery_cache/documents/jobs.v3p1beta1.json

@@ -682,7 +682,7 @@
 }
 }
 },
-"revision": "20240620",
+"revision": "20241219",
 "rootUrl": "https://jobs.googleapis.com/",
 "schemas": {
 "ApplicationInfo": {
@@ -2452,18 +2452,18 @@ false
 "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": {
@@ -2479,7 +2479,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 (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": {
@@ -2499,7 +2499,7 @@ 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 (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": {
@@ -2781,22 +2781,22 @@ false
 "id": "TimeOfDay",
 "properties": {
 "hours": {
-"description": "Hours of day in 24 hour format. Should be from 0 to 23. An API may choose to allow the value \"24:00:00\" for scenarios like business closing time.",
+"description": "Hours of a day in 24 hour format. Must be greater than or equal to 0 and typically must be less than or equal to 23. An API may choose to allow the value \"24:00:00\" for scenarios like business closing time.",
 "format": "int32",
 "type": "integer"
 },
 "minutes": {
-"description": "Minutes of hour of day. Must be from 0 to 59.",
+"description": "Minutes of an hour. Must be greater than or equal to 0 and less than or equal to 59.",
 "format": "int32",
 "type": "integer"
 },
 "nanos": {
-"description": "Fractions of seconds in nanoseconds. Must be from 0 to 999,999,999.",
+"description": "Fractions of seconds, in nanoseconds. Must be greater than or equal to 0 and less than or equal to 999,999,999.",
 "format": "int32",
 "type": "integer"
 },
 "seconds": {
-"description": "Seconds of minutes of the time. Must normally be from 0 to 59. An API may allow the value 60 if it allows leap-seconds.",
+"description": "Seconds of a minute. Must be greater than or equal to 0 and typically must be less than or equal to 59. An API may allow the value 60 if it allows leap-seconds.",
 "format": "int32",
 "type": "integer"
 }

googleapiclient/discovery_cache/documents/jobs.v4.json

@@ -903,7 +903,7 @@
 }
 }
 },
-"revision": "20240620",
+"revision": "20241217",
 "rootUrl": "https://jobs.googleapis.com/",
 "schemas": {
 "ApplicationInfo": {
@@ -1829,7 +1829,7 @@
 "type": "string"
 },
 "postingExpireTime": {
-"description": "Strongly recommended for the best service experience. The expiration timestamp of the job. After this timestamp, the job is marked as expired, and it no longer appears in search results. The expired job can't be listed by the ListJobs API, but it can be retrieved with the GetJob API or updated with the UpdateJob API or deleted with the DeleteJob API. An expired job can be updated and opened again by using a future expiration timestamp. Updating an expired job fails if there is another existing open job with same company, language_code and requisition_id. The expired jobs are retained in our system for 90 days. However, the overall expired job count cannot exceed 3 times the maximum number of open jobs over previous 7 days. If this threshold is exceeded, expired jobs are cleaned out in order of earliest expire time. Expired jobs are no longer accessible after they are cleaned out. Invalid timestamps are ignored, and treated as expire time not provided. If the timestamp is before the instant request is made, the job is treated as expired immediately on creation. This kind of job can not be updated. And when creating a job with past timestamp, the posting_publish_time must be set before posting_expire_time. The purpose of this feature is to allow other objects, such as Application, to refer a job that didn't exist in the system prior to becoming expired. If you want to modify a job that was expired on creation, delete it and create a new one. If this value isn't provided at the time of job creation or is invalid, the job posting expires after 30 days from the job's creation time. For example, if the job was created on 2017/01/01 13:00AM UTC with an unspecified expiration date, the job expires after 2017/01/31 13:00AM UTC. If this value isn't provided on job update, it depends on the field masks set by UpdateJobRequest.update_mask. If the field masks include job_end_time, or the masks are empty meaning that every field is updated, the job posting expires after 30 days from the job's last update time. Otherwise the expiration date isn't updated.",
+"description": "Strongly recommended for the best service experience. The expiration timestamp of the job. After this timestamp, the job is marked as expired, and it no longer appears in search results. The expired job can't be listed by the ListJobs API, but it can be retrieved with the GetJob API or updated with the UpdateJob API or deleted with the DeleteJob API. An expired job can be updated and opened again by using a future expiration timestamp. Updating an expired job fails if there is another existing open job with same company, language_code and requisition_id. The expired jobs are retained in our system for 90 days. However, the overall expired job count cannot exceed 3 times the maximum number of open jobs over previous 7 days. If this threshold is exceeded, expired jobs are cleaned out in order of earliest expire time. Expired jobs are no longer accessible after they are cleaned out. Invalid timestamps are ignored, and treated as expire time not provided. If the timestamp is before the instant request is made, the job is treated as expired immediately on creation. This kind of job can not be updated. And when creating a job with past timestamp, the posting_publish_time must be set before posting_expire_time. The purpose of this feature is to allow other objects, such as ApplicationInfo, to refer a job that didn't exist in the system prior to becoming expired. If you want to modify a job that was expired on creation, delete it and create a new one. If this value isn't provided at the time of job creation or is invalid, the job posting expires after 30 days from the job's creation time. For example, if the job was created on 2017/01/01 13:00AM UTC with an unspecified expiration date, the job expires after 2017/01/31 13:00AM UTC. If this value isn't provided on job update, it depends on the field masks set by UpdateJobRequest.update_mask. If the field masks include job_end_time, or the masks are empty meaning that every field is updated, the job posting expires after 30 days from the job's last update time. Otherwise the expiration date isn't updated.",
 "format": "google-datetime",
 "type": "string"
 },
@@ -2392,7 +2392,7 @@
 "type": "string"
 },
 "telecommutePreference": {
-"description": "Allows the client to return jobs without a set location, specifically, telecommuting jobs (telecommuting is considered by the service as a special location). Job.posting_region indicates if a job permits telecommuting. If this field is set to TelecommutePreference.TELECOMMUTE_ALLOWED, telecommuting jobs are searched, and address and lat_lng are ignored. If not set or set to TelecommutePreference.TELECOMMUTE_EXCLUDED, the telecommute status of the jobs is ignored. Jobs that have PostingRegion.TELECOMMUTE and have additional Job.addresses may still be matched based on other location filters using address or latlng. This filter can be used by itself to search exclusively for telecommuting jobs, or it can be combined with another location filter to search for a combination of job locations, such as \"Mountain View\" or \"telecommuting\" jobs. However, when used in combination with other location filters, telecommuting jobs can be treated as less relevant than other jobs in the search response. This field is only used for job search requests.",
+"description": "Allows the client to return jobs without a set location, specifically, telecommuting jobs (telecommuting is considered by the service as a special location). Job.posting_region indicates if a job permits telecommuting. If this field is set to TelecommutePreference.TELECOMMUTE_ALLOWED, telecommuting jobs are searched, and address and lat_lng are ignored. If not set or set to TelecommutePreference.TELECOMMUTE_EXCLUDED, the telecommute status of the jobs is ignored. Jobs that have PostingRegion.TELECOMMUTE and have additional Job.addresses may still be matched based on other location filters using address or lat_lng. This filter can be used by itself to search exclusively for telecommuting jobs, or it can be combined with another location filter to search for a combination of job locations, such as \"Mountain View\" or \"telecommuting\" jobs. However, when used in combination with other location filters, telecommuting jobs can be treated as less relevant than other jobs in the search response. This field is only used for job search requests.",
 "enum": [
 "TELECOMMUTE_PREFERENCE_UNSPECIFIED",
 "TELECOMMUTE_EXCLUDED",
@@ -2500,18 +2500,18 @@ false
 "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": {
@@ -2527,7 +2527,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 (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": {
@@ -2547,7 +2547,7 @@ 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 (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": {
@@ -2722,6 +2722,24 @@ false
 "description": "The token specifying the current offset within search results. See SearchJobsResponse.next_page_token for an explanation of how to obtain the next set of query results.",
 "type": "string"
 },
+"relevanceThreshold": {
+"description": "Optional. The relevance threshold of the search results. Default to Google defined threshold, leveraging a balance of precision and recall to deliver both highly accurate results and comprehensive coverage of relevant information.",
+"enum": [
+"RELEVANCE_THRESHOLD_UNSPECIFIED",
+"LOWEST",
+"LOW",
+"MEDIUM",
+"HIGH"
+],
+"enumDescriptions": [
+"Default value. In this case, server behavior defaults to Google defined threshold.",
+"Lowest relevance threshold.",
+"Low relevance threshold.",
+"Medium relevance threshold.",
+"High relevance threshold."
+],
+"type": "string"
+},
 "requestMetadata": {
 "$ref": "RequestMetadata",
 "description": "Required. The meta information collected about the job searcher, used to improve the search quality of the service. The identifiers (such as `user_id`) are provided by users, and must be unique and consistent."
@@ -2859,22 +2877,22 @@ false
 "id": "TimeOfDay",
 "properties": {
 "hours": {
-"description": "Hours of day in 24 hour format. Should be from 0 to 23. An API may choose to allow the value \"24:00:00\" for scenarios like business closing time.",
+"description": "Hours of a day in 24 hour format. Must be greater than or equal to 0 and typically must be less than or equal to 23. An API may choose to allow the value \"24:00:00\" for scenarios like business closing time.",
 "format": "int32",
 "type": "integer"
 },
 "minutes": {
-"description": "Minutes of hour of day. Must be from 0 to 59.",
+"description": "Minutes of an hour. Must be greater than or equal to 0 and less than or equal to 59.",
 "format": "int32",
 "type": "integer"
 },
 "nanos": {
-"description": "Fractions of seconds in nanoseconds. Must be from 0 to 999,999,999.",
+"description": "Fractions of seconds, in nanoseconds. Must be greater than or equal to 0 and less than or equal to 999,999,999.",
 "format": "int32",
 "type": "integer"
 },
 "seconds": {
-"description": "Seconds of minutes of the time. Must normally be from 0 to 59. An API may allow the value 60 if it allows leap-seconds.",
+"description": "Seconds of a minute. Must be greater than or equal to 0 and typically must be less than or equal to 59. An API may allow the value 60 if it allows leap-seconds.",
 "format": "int32",
 "type": "integer"
 }

googleapiclient/discovery_cache/documents/merchantapi.products_v1beta.json

@@ -242,7 +242,7 @@
 }
 }
 },
-"revision": "20241211",
+"revision": "20241217",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Attributes": {
@@ -651,6 +651,13 @@
 "$ref": "SubscriptionCost",
 "description": "Number of periods (months or years) and amount of payment per period for an item with an associated subscription contract."
 },
+"sustainabilityIncentives": {
+"description": "The list of sustainability incentive programs.",
+"items": {
+"$ref": "ProductSustainabilityIncentive"
+},
+"type": "array"
+},
 "taxCategory": {
 "description": "The tax category of the product.",
 "type": "string"
@@ -1516,6 +1523,36 @@ false
 },
 "type": "object"
 },
+"ProductSustainabilityIncentive": {
+"description": "Information regarding sustainability-related incentive programs such as rebates or tax relief.",
+"id": "ProductSustainabilityIncentive",
+"properties": {
+"amount": {
+"$ref": "Price",
+"description": "The fixed amount of the incentive."
+},
+"percentage": {
+"description": "The percentage of the sale price that the incentive is applied to.",
+"format": "double",
+"type": "number"
+},
+"type": {
+"description": "Sustainability incentive program.",
+"enum": [
+"TYPE_UNSPECIFIED",
+"EV_TAX_CREDIT",
+"EV_PRICE_DISCOUNT"
+],
+"enumDescriptions": [
+"Unspecified or unknown sustainability incentive type.",
+"Program offering tax liability reductions for electric vehicles and, in some countries, plug-in hybrids. These reductions can be based on a specific amount or a percentage of the sale price.",
+"A subsidy program, often called an environmental bonus, provides a purchase grant for electric vehicles and, in some countries, plug-in hybrids. The grant amount may be a fixed sum or a percentage of the sale price."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "ProductWeight": {
 "description": "The weight of the product.",
 "id": "ProductWeight",

googleapiclient/discovery_cache/documents/migrationcenter.v1alpha1.json

@@ -2548,7 +2548,7 @@
 }
 }
 },
-"revision": "20241205",
+"revision": "20241212",
 "rootUrl": "https://migrationcenter.googleapis.com/",
 "schemas": {
 "AddAssetsToGroupRequest": {
@@ -6620,6 +6620,11 @@ false
 "format": "int32",
 "readOnly": true,
 "type": "integer"
+},
+"xlsxOutputFile": {
+"$ref": "XlsxOutputFile",
+"description": "Output only. XLSX output file.",
+"readOnly": true
 }
 },
 "type": "object"
@@ -7858,7 +7863,22 @@ false
 "SignedUriDestination": {
 "description": "Signed URI destination configuration.",
 "id": "SignedUriDestination",
-"properties": {},
+"properties": {
+"fileFormat": {
+"description": "Required. The file format to export.",
+"enum": [
+"FILE_FORMAT_UNSPECIFIED",
+"CSV",
+"XLSX"
+],
+"enumDescriptions": [
+"Unspecified file format will be treated as CSV.",
+"CSV file format.",
+"XLSX file format which used in Excel."
+],
+"type": "string"
+}
+},
 "type": "object"
 },
 "SignedUris": {
@@ -8798,6 +8818,18 @@ false
 }
 },
 "type": "object"
+},
+"XlsxOutputFile": {
+"description": "Contains a single output file of type XLSX.",
+"id": "XlsxOutputFile",
+"properties": {
+"signedUri": {
+"$ref": "SignedUri",
+"description": "Output only. Signed URI destination.",
+"readOnly": true
+}
+},
+"type": "object"
 }
 },
 "servicePath": "",

googleapiclient/discovery_cache/documents/monitoring.v1.json

@@ -753,7 +753,7 @@
 }
 }
 },
-"revision": "20241003",
+"revision": "20241212",
 "rootUrl": "https://monitoring.googleapis.com/",
 "schemas": {
 "Aggregation": {
@@ -1060,6 +1060,33 @@
 },
 "type": "object"
 },
+"ColumnSortingOptions": {
+"description": "Data structure to storing column's sort strategy",
+"id": "ColumnSortingOptions",
+"properties": {
+"column": {
+"description": "Optional. Column name to sort data by",
+"type": "string"
+},
+"direction": {
+"description": "Optional. A sorting direction that determines ascending or descending order. This is a legacy field kept for backwards compatibility with table.",
+"enum": [
+"SORT_ORDER_UNSPECIFIED",
+"SORT_ORDER_NONE",
+"SORT_ORDER_ASCENDING",
+"SORT_ORDER_DESCENDING"
+],
+"enumDescriptions": [
+"An unspecified sort order. This option is invalid when sorting is required.",
+"No sorting is applied.",
+"The lowest-valued entries are selected first.",
+"The highest-valued entries are selected first."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "Dashboard": {
 "description": "A Google Stackdriver dashboard. Dashboards define the content and layout of pages in the Stackdriver web application.",
 "id": "Dashboard",
@@ -1253,6 +1280,13 @@
 ],
 "type": "string"
 },
+"sort": {
+"description": "Optional. A collection of sort options, affects the order of the data and legend.",
+"items": {
+"$ref": "ColumnSortingOptions"
+},
+"type": "array"
+},
 "targetAxis": {
 "description": "Optional. The target axis to use for plotting the metric.",
 "enum": [

googleapiclient/discovery_cache/documents/pubsub.v1.json

@@ -1638,7 +1638,7 @@
 }
 }
 },
-"revision": "20240918",
+"revision": "20241212",
 "rootUrl": "https://pubsub.googleapis.com/",
 "schemas": {
 "AcknowledgeRequest": {
@@ -1656,7 +1656,7 @@
 "type": "object"
 },
 "AnalyticsHubSubscriptionInfo": {
-"description": "Information about an associated Analytics Hub subscription (https://cloud.google.com/bigquery/docs/analytics-hub-manage-subscriptions).",
+"description": "Information about an associated [Analytics Hub subscription](https://cloud.google.com/bigquery/docs/analytics-hub-manage-subscriptions).",
 "id": "AnalyticsHubSubscriptionInfo",
 "properties": {
 "listing": {