feat(chromemanagement): update the api

#### chromemanagement:v1

The following keys were deleted:
- schemas.GoogleChromeManagementVersionsV1CertificateProvisioningProcess.properties.caConnectionAdapterConfigReference (Total Keys: 2)
- schemas.GoogleChromeManagementVersionsV1CertificateProvisioningProcess.properties.profileAdapterConfigReference (Total Keys: 2)

Author: yoshi-automation

docs/dyn/chromemanagement_v1.customers.profiles.html

@@ -156,7 +156,7 @@ <h3>Method Details</h3>
   &quot;lastStatusReportTime&quot;: &quot;A String&quot;, # Output only. Timestamp of the latest status report by the profile.
   &quot;name&quot;: &quot;A String&quot;, # Identifier. Format: customers/{customer_id}/profiles/{profile_permanent_id}
   &quot;osPlatformType&quot;: &quot;A String&quot;, # Output only. OS platform of the device on which the profile exists.
-  &quot;osPlatformVersion&quot;: &quot;A String&quot;, # Output only. Major OS version of the device on which the profile exists. (i.e. Windows 10)
+  &quot;osPlatformVersion&quot;: &quot;A String&quot;, # Output only. Major OS platform version of the device on which the profile exists, from profile reporting.
   &quot;osVersion&quot;: &quot;A String&quot;, # Output only. OS version of the device on which the profile exists.
   &quot;policyCount&quot;: &quot;A String&quot;, # Output only. Number of policies applied on the profile.
   &quot;profileId&quot;: &quot;A String&quot;, # Output only. Chrome client side profile ID.
@@ -226,8 +226,8 @@ <h3>Method Details</h3>
 
 Args:
   parent: string, Required. Format: customers/{customer_id} (required)
-  filter: string, Optional. The filter used to filter profiles. The following fields can be used in the filter: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state - ouId Any of the above fields can be used to specify a filter, and filtering by multiple fields is supported with AND operator. String type fields and enum type fields support &#x27;=&#x27; and &#x27;!=&#x27; operators. The integer type and the timestamp type fields support &#x27;=&#x27;, &#x27;!=&#x27;, &#x27;&lt;&#x27;, &#x27;&gt;&#x27;, &#x27;&lt;=&#x27; and &#x27;&gt;=&#x27; operators. Timestamps expect an RFC-3339 formatted string (e.g. 2012-04-21T11:30:00-04:00). Wildcard &#x27;*&#x27; can be used with a string type field filter. In addition, string literal filtering is also supported, for example, &#x27;ABC&#x27; as a filter maps to a filter that checks if any of the filterable string type fields contains &#x27;ABC&#x27;. Organization unit number can be used as a filtering criteria here by specifying &#x27;ouId = ${your_org_unit_id}&#x27;, please note that only single OU ID matching is supported.
-  orderBy: string, Optional. The fields used to specify the ordering of the results. The supported fields are: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state By default, sorting is in ascending order, to specify descending order for a field, a suffix &quot; desc&quot; should be added to the field name. The default ordering is the descending order of last_status_report_time.
+  filter: string, Optional. The filter used to filter profiles. The following fields can be used in the filter: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state - os_platform_version - ouId Any of the above fields can be used to specify a filter, and filtering by multiple fields is supported with AND operator. String type fields and enum type fields support &#x27;=&#x27; and &#x27;!=&#x27; operators. The integer type and the timestamp type fields support &#x27;=&#x27;, &#x27;!=&#x27;, &#x27;&lt;&#x27;, &#x27;&gt;&#x27;, &#x27;&lt;=&#x27; and &#x27;&gt;=&#x27; operators. Timestamps expect an RFC-3339 formatted string (e.g. 2012-04-21T11:30:00-04:00). Wildcard &#x27;*&#x27; can be used with a string type field filter. In addition, string literal filtering is also supported, for example, &#x27;ABC&#x27; as a filter maps to a filter that checks if any of the filterable string type fields contains &#x27;ABC&#x27;. Organization unit number can be used as a filtering criteria here by specifying &#x27;ouId = ${your_org_unit_id}&#x27;, please note that only single OU ID matching is supported.
+  orderBy: string, Optional. The fields used to specify the ordering of the results. The supported fields are: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state - os_platform_version By default, sorting is in ascending order, to specify descending order for a field, a suffix &quot; desc&quot; should be added to the field name. The default ordering is the descending order of last_status_report_time.
   pageSize: integer, Optional. The maximum number of profiles to return. The default page size is 100 if page_size is unspecified, and the maximum page size allowed is 200.
   pageToken: string, Optional. The page token used to retrieve a specific page of the listing request.
   x__xgafv: string, V1 error format.
@@ -269,7 +269,7 @@ <h3>Method Details</h3>
       &quot;lastStatusReportTime&quot;: &quot;A String&quot;, # Output only. Timestamp of the latest status report by the profile.
       &quot;name&quot;: &quot;A String&quot;, # Identifier. Format: customers/{customer_id}/profiles/{profile_permanent_id}
       &quot;osPlatformType&quot;: &quot;A String&quot;, # Output only. OS platform of the device on which the profile exists.
-      &quot;osPlatformVersion&quot;: &quot;A String&quot;, # Output only. Major OS version of the device on which the profile exists. (i.e. Windows 10)
+      &quot;osPlatformVersion&quot;: &quot;A String&quot;, # Output only. Major OS platform version of the device on which the profile exists, from profile reporting.
       &quot;osVersion&quot;: &quot;A String&quot;, # Output only. OS version of the device on which the profile exists.
       &quot;policyCount&quot;: &quot;A String&quot;, # Output only. Number of policies applied on the profile.
       &quot;profileId&quot;: &quot;A String&quot;, # Output only. Chrome client side profile ID.

googleapiclient/discovery_cache/documents/chromemanagement.v1.json

@@ -413,12 +413,12 @@
 ],
 "parameters": {
 "filter": {
-"description": "Optional. The filter used to filter profiles. The following fields can be used in the filter: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state - ouId Any of the above fields can be used to specify a filter, and filtering by multiple fields is supported with AND operator. String type fields and enum type fields support '=' and '!=' operators. The integer type and the timestamp type fields support '=', '!=', '<', '>', '<=' and '>=' operators. Timestamps expect an RFC-3339 formatted string (e.g. 2012-04-21T11:30:00-04:00). Wildcard '*' can be used with a string type field filter. In addition, string literal filtering is also supported, for example, 'ABC' as a filter maps to a filter that checks if any of the filterable string type fields contains 'ABC'. Organization unit number can be used as a filtering criteria here by specifying 'ouId = ${your_org_unit_id}', please note that only single OU ID matching is supported.",
+"description": "Optional. The filter used to filter profiles. The following fields can be used in the filter: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state - os_platform_version - ouId Any of the above fields can be used to specify a filter, and filtering by multiple fields is supported with AND operator. String type fields and enum type fields support '=' and '!=' operators. The integer type and the timestamp type fields support '=', '!=', '<', '>', '<=' and '>=' operators. Timestamps expect an RFC-3339 formatted string (e.g. 2012-04-21T11:30:00-04:00). Wildcard '*' can be used with a string type field filter. In addition, string literal filtering is also supported, for example, 'ABC' as a filter maps to a filter that checks if any of the filterable string type fields contains 'ABC'. Organization unit number can be used as a filtering criteria here by specifying 'ouId = ${your_org_unit_id}', please note that only single OU ID matching is supported.",
 "location": "query",
 "type": "string"
 },
 "orderBy": {
-"description": "Optional. The fields used to specify the ordering of the results. The supported fields are: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state By default, sorting is in ascending order, to specify descending order for a field, a suffix \" desc\" should be added to the field name. The default ordering is the descending order of last_status_report_time.",
+"description": "Optional. The fields used to specify the ordering of the results. The supported fields are: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state - os_platform_version By default, sorting is in ascending order, to specify descending order for a field, a suffix \" desc\" should be added to the field name. The default ordering is the descending order of last_status_report_time.",
 "location": "query",
 "type": "string"
 },
@@ -1280,7 +1280,7 @@
 }
 }
 },
-"revision": "20250307",
+"revision": "20250313",
 "rootUrl": "https://chromemanagement.googleapis.com/",
 "schemas": {
 "GoogleChromeManagementV1AndroidAppInfo": {
@@ -5015,23 +5015,18 @@ false
 "description": "A certificate provisioning process.",
 "id": "GoogleChromeManagementVersionsV1CertificateProvisioningProcess",
 "properties": {
-"caConnectionAdapterConfigReference": {
-"description": "Output only. A JSON string that contains the administrator-provided configuration for the certification authority service. This field can be missing if no configuration was given.",
-"readOnly": true,
-"type": "string"
-},
 "chromeOsDevice": {
 "$ref": "GoogleChromeManagementVersionsV1ChromeOsDevice",
 "description": "Output only. The client certificate is being provisioned for a ChromeOS device. This contains information about the device.",
 "readOnly": true
 },
 "chromeOsUserSession": {
 "$ref": "GoogleChromeManagementVersionsV1ChromeOsUserSession",
-"description": "Output only. The client certificate is being provisioned for a ChromeOS user session. This contains information about the user session.",
+"description": "Output only. The client certificate is being provisioned for a ChromeOS user. This contains information about the current user session.",
 "readOnly": true
 },
 "failureMessage": {
-"description": "Output only. A message describing why this `CertificateProvisioningProcess` failed. Presence of this field indicates that the `CertificateProvisioningProcess` has failed.",
+"description": "Output only. A message describing why this `CertificateProvisioningProcess` has failed. Presence of this field indicates that the `CertificateProvisioningProcess` has failed.",
 "readOnly": true,
 "type": "string"
 },
@@ -5054,11 +5049,6 @@ false
 "description": "Identifier. Resource name of the `CertificateProvisioningProcess`. The name pattern is given as `customers/{customer}/certificateProvisioningProcesses/{certificate_provisioning_process}` with `{customer}` being the obfuscated customer id and `{certificate_provisioning_process}` being the certificate provisioning process id.",
 "type": "string"
 },
-"profileAdapterConfigReference": {
-"description": "Output only. A JSON string that contains the administrator-provided configuration for the certificate provisioning profile. This field can be missing if no configuration was given.",
-"readOnly": true,
-"type": "string"
-},
 "provisioningProfileId": {
 "description": "Output only. The ID of the certificate provisioning profile.",
 "readOnly": true,
@@ -5071,7 +5061,7 @@ false
 "type": "string"
 },
 "signature": {
-"description": "Output only. The signature of `signature_algorithm`, generated using the client's private key using `signature_algorithm`. This field is only present after the`SignData` operation has finished.",
+"description": "Output only. The signature of `signature_algorithm`, generated using the client's private key using `signature_algorithm`. This field is only present after the `SignData` operation has finished.",
 "format": "byte",
 "readOnly": true,
 "type": "string"
@@ -5080,13 +5070,11 @@ false
 "description": "Output only. The signature algorithm that the adapter expects the client and backend components to use when processing `sign_data`. This field is only present after the `SignData` operation has been initiated.",
 "enum": [
 "SIGNATURE_ALGORITHM_UNSPECIFIED",
-"SIGNATURE_ALGORITHM_RSA_PKCS1_V1_5_SHA256",
-"SIGNATURE_ALGORITHM_ECDSA_SHA256"
+"SIGNATURE_ALGORITHM_RSA_PKCS1_V1_5_SHA256"
 ],
 "enumDescriptions": [
 "Default value. This value is unused.",
-"The server-side builds the PKCS#1 DigestInfo, i.e., the SHA256 hash is constructed on the server-side. The client should sign using RSA with PKCS#1 v1.5 padding.",
-"The PKCS#1 digest info is built by the server-side and sent to the client unhashed. The client is responsible for signing and hashing. Uses the P-256 curve."
+"The server-side builds the PKCS#1 DigestInfo, i.e., the SHA256 hash is constructed on the server-side. The client should sign using RSA with PKCS#1 v1.5 padding."
 ],
 "readOnly": true,
 "type": "string"
@@ -5230,7 +5218,7 @@ false
 "type": "string"
 },
 "osPlatformVersion": {
-"description": "Output only. Major OS version of the device on which the profile exists. (i.e. Windows 10)",
+"description": "Output only. Major OS platform version of the device on which the profile exists, from profile reporting.",
 "readOnly": true,
 "type": "string"
 },
@@ -5296,7 +5284,7 @@ false
 "properties": {
 "chromeOsDevice": {
 "$ref": "GoogleChromeManagementVersionsV1ChromeOsDevice",
-"description": "Output only. This field contains information about the ChromeOS device that the user session is running on. It is only set if the user session is affiliated, i.e. if the user is managed by the same organization that managed the ChromeOS device.",
+"description": "Output only. This field contains information about the ChromeOS device that the user session is running on. It is only set if the user is affiliated, i.e., if the user is managed by the same organization that manages the ChromeOS device.",
 "readOnly": true
 },
 "userDirectoryApiId": {