chore(androiddeviceprovisioning): update the api

Author: yoshi-automation

docs/dyn/androiddeviceprovisioning_v1.customers.configurations.html

@@ -103,7 +103,7 @@ <h3>Method Details</h3>
   <pre>Creates a new configuration. Once created, a customer can apply the configuration to devices.
 
 Args:
-  parent: string, Required. The customer that manages the configuration. An API resource name in the format `customers/[CUSTOMER_ID]`. (required)
+  parent: string, Required. The customer that manages the configuration. An API resource name in the format `customers/[CUSTOMER_ID]`. This field has custom validation in CreateConfigurationRequestValidator (required)
   body: object, The request body.
     The object takes the form of:
 

docs/dyn/androiddeviceprovisioning_v1.customers.devices.html

@@ -107,7 +107,7 @@ <h3>Method Details</h3>
 
 { # Request message for customer to assign a configuration to device.
   &quot;configuration&quot;: &quot;A String&quot;, # Required. The configuration applied to the device in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`.
-  &quot;device&quot;: { # A `DeviceReference` is an API abstraction that lets you supply a _device_ argument to a method using one of the following identifier types: * A numeric API resource ID. * Real-world hardware IDs, such as IMEI number, belonging to the manufactured device. Methods that operate on devices take a `DeviceReference` as a parameter type because it&#x27;s more flexible for the caller. To learn more about device identifiers, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. The device the configuration is applied to.
+  &quot;device&quot;: { # A `DeviceReference` is an API abstraction that lets you supply a _device_ argument to a method using one of the following identifier types: * A numeric API resource ID. * Real-world hardware IDs, such as IMEI number, belonging to the manufactured device. Methods that operate on devices take a `DeviceReference` as a parameter type because it&#x27;s more flexible for the caller. To learn more about device identifiers, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. The device the configuration is applied to. There are custom validations in ApplyConfigurationRequestValidator
     &quot;deviceId&quot;: &quot;A String&quot;, # The ID of the device.
     &quot;deviceIdentifier&quot;: { # Encapsulates hardware and product IDs to identify a manufactured device. To understand requirements on identifier sets, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # The hardware IDs of the device.
       &quot;imei&quot;: &quot;A String&quot;, # The device’s IMEI number. Validated on input.
@@ -253,7 +253,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # Request message for customer to remove the configuration from device.
-  &quot;device&quot;: { # A `DeviceReference` is an API abstraction that lets you supply a _device_ argument to a method using one of the following identifier types: * A numeric API resource ID. * Real-world hardware IDs, such as IMEI number, belonging to the manufactured device. Methods that operate on devices take a `DeviceReference` as a parameter type because it&#x27;s more flexible for the caller. To learn more about device identifiers, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. The device to remove the configuration from.
+  &quot;device&quot;: { # A `DeviceReference` is an API abstraction that lets you supply a _device_ argument to a method using one of the following identifier types: * A numeric API resource ID. * Real-world hardware IDs, such as IMEI number, belonging to the manufactured device. Methods that operate on devices take a `DeviceReference` as a parameter type because it&#x27;s more flexible for the caller. To learn more about device identifiers, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. The device to remove the configuration from. There are custom validations in RemoveConfigurationRequestValidator
     &quot;deviceId&quot;: &quot;A String&quot;, # The ID of the device.
     &quot;deviceIdentifier&quot;: { # Encapsulates hardware and product IDs to identify a manufactured device. To understand requirements on identifier sets, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # The hardware IDs of the device.
       &quot;imei&quot;: &quot;A String&quot;, # The device’s IMEI number. Validated on input.
@@ -287,7 +287,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # Request message for customer to unclaim a device.
-  &quot;device&quot;: { # A `DeviceReference` is an API abstraction that lets you supply a _device_ argument to a method using one of the following identifier types: * A numeric API resource ID. * Real-world hardware IDs, such as IMEI number, belonging to the manufactured device. Methods that operate on devices take a `DeviceReference` as a parameter type because it&#x27;s more flexible for the caller. To learn more about device identifiers, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. The device to unclaim.
+  &quot;device&quot;: { # A `DeviceReference` is an API abstraction that lets you supply a _device_ argument to a method using one of the following identifier types: * A numeric API resource ID. * Real-world hardware IDs, such as IMEI number, belonging to the manufactured device. Methods that operate on devices take a `DeviceReference` as a parameter type because it&#x27;s more flexible for the caller. To learn more about device identifiers, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. The device to unclaim. There are custom validations in UnclaimDeviceRequestValidator.
     &quot;deviceId&quot;: &quot;A String&quot;, # The ID of the device.
     &quot;deviceIdentifier&quot;: { # Encapsulates hardware and product IDs to identify a manufactured device. To understand requirements on identifier sets, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # The hardware IDs of the device.
       &quot;imei&quot;: &quot;A String&quot;, # The device’s IMEI number. Validated on input.

docs/dyn/androiddeviceprovisioning_v1.customers.html

@@ -110,7 +110,7 @@ <h3>Method Details</h3>
 
 Args:
   pageSize: integer, The maximum number of customers to show in a page of results. A number between 1 and 100 (inclusive).
-  pageToken: string, A token specifying which result page to return.
+  pageToken: string, A token specifying which result page to return. This field has custom validations in ListCustomersRequestValidator
   x__xgafv: string, V1 error format.
     Allowed values
       1 - v1 error format

googleapiclient/discovery_cache/documents/androiddeviceprovisioning.v1.json

@@ -112,7 +112,7 @@
               "type": "integer"
             },
             "pageToken": {
-              "description": "A token specifying which result page to return.",
+              "description": "A token specifying which result page to return. This field has custom validations in ListCustomersRequestValidator",
               "location": "query",
               "type": "string"
             }
@@ -136,7 +136,7 @@
               ],
               "parameters": {
                 "parent": {
-                  "description": "Required. The customer that manages the configuration. An API resource name in the format `customers/[CUSTOMER_ID]`.",
+                  "description": "Required. The customer that manages the configuration. An API resource name in the format `customers/[CUSTOMER_ID]`. This field has custom validation in CreateConfigurationRequestValidator",
                   "location": "path",
                   "pattern": "^customers/[^/]+$",
                   "required": true,
@@ -825,7 +825,7 @@
       }
     }
   },
-  "revision": "20220202",
+  "revision": "20220212",
   "rootUrl": "https://androiddeviceprovisioning.googleapis.com/",
   "schemas": {
     "ClaimDeviceRequest": {
@@ -1024,7 +1024,7 @@
         },
         "device": {
           "$ref": "DeviceReference",
-          "description": "Required. The device the configuration is applied to."
+          "description": "Required. The device the configuration is applied to. There are custom validations in ApplyConfigurationRequestValidator"
         }
       },
       "type": "object"
@@ -1099,7 +1099,7 @@
       "properties": {
         "device": {
           "$ref": "DeviceReference",
-          "description": "Required. The device to remove the configuration from."
+          "description": "Required. The device to remove the configuration from. There are custom validations in RemoveConfigurationRequestValidator"
         }
       },
       "type": "object"
@@ -1110,7 +1110,7 @@
       "properties": {
         "device": {
           "$ref": "DeviceReference",
-          "description": "Required. The device to unclaim."
+          "description": "Required. The device to unclaim. There are custom validations in UnclaimDeviceRequestValidator."
         }
       },
       "type": "object"