chore: Update discovery artifacts

docs/dyn/admin_directory_v1.customers.chrome.printers.html

@@ -93,7 +93,7 @@ <h2>Instance Methods</h2>
   <code><a href="#get">get(name, x__xgafv=None)</a></code></p>
 <p class="firstline">Returns a `Printer` resource (printer's config).</p>
 <p class="toc_element">
-  <code><a href="#list">list(parent, filter=None, orgUnitId=None, pageSize=None, pageToken=None, x__xgafv=None)</a></code></p>
+  <code><a href="#list">list(parent, filter=None, orderBy=None, orgUnitId=None, pageSize=None, pageToken=None, x__xgafv=None)</a></code></p>
 <p class="firstline">List printers configs.</p>
 <p class="toc_element">
   <code><a href="#listPrinterModels">listPrinterModels(parent, filter=None, pageSize=None, pageToken=None, x__xgafv=None)</a></code></p>
@@ -369,12 +369,13 @@ <h3>Method Details</h3>
 </div>
 
 <div class="method">
-    <code class="details" id="list">list(parent, filter=None, orgUnitId=None, pageSize=None, pageToken=None, x__xgafv=None)</code>
+    <code class="details" id="list">list(parent, filter=None, orderBy=None, orgUnitId=None, pageSize=None, pageToken=None, x__xgafv=None)</code>
   <pre>List printers configs.
 
 Args:
   parent: string, Required. The name of the customer who owns this collection of printers. Format: customers/{customer_id} (required)
   filter: string, Search query. Search syntax is shared between this api and Admin Console printers pages.
+  orderBy: string, The order to sort results by. Must be one of display_name, description, make_and_model, or create_time. Default order is ascending, but descending order can be returned by appending &quot;desc&quot; to the order_by field. For instance, &quot;description desc&quot; will return the printers sorted by description in descending order.
   orgUnitId: string, Organization Unit that we want to list the printers for. When org_unit is not present in the request then all printers of the customer are returned (or filtered). When org_unit is present in the request then only printers available to this OU will be returned (owned or inherited). You may see if printer is owned or inherited for this OU by looking at Printer.org_unit_id.
   pageSize: integer, The maximum number of objects to return. The service may return fewer than this value.
   pageToken: string, A page token, received from a previous call.

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