chore: Update discovery artifacts (#1325)
## Deleted keys were detected in the following stable discovery artifacts:
apigeev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/9106808da3e03faa4c27913358e0c07edd82ff5a)
## Discovery Artifact Change Summary:
apigeev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/9106808da3e03faa4c27913358e0c07edd82ff5a)
dataflowv1b3[ [More details]](https://github.com/googleapis/google-api-python-client/commit/9dd646184e70a83831f3347fc01a3eb0090ca0e8)
dialogflowv2[ [More details]](https://github.com/googleapis/google-api-python-client/commit/a7f2e96e6b283771e986d9ec7f1f057ff67e2a29)
dialogflowv2beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/a7f2e96e6b283771e986d9ec7f1f057ff67e2a29)
dialogflowv3[ [More details]](https://github.com/googleapis/google-api-python-client/commit/a7f2e96e6b283771e986d9ec7f1f057ff67e2a29)
documentaiv1beta3[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ee1318d36230ff4b7393ce1f15d6a9ee71d23cea)
healthcarev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/1204c1d486e08630773812ff1cc35843d98eb1d8)
feat(apigee): update the api
feat(dataflow): update the api
feat(dialogflow): update the api
feat(documentai): update the api
feat(healthcare): update the api
diff --git a/docs/dyn/documentai_v1beta3.projects.locations.html b/docs/dyn/documentai_v1beta3.projects.locations.html
index 6fc99bf..d34c57d 100644
--- a/docs/dyn/documentai_v1beta3.projects.locations.html
+++ b/docs/dyn/documentai_v1beta3.projects.locations.html
@@ -88,6 +88,9 @@
<code><a href="#close">close()</a></code></p>
<p class="firstline">Close httplib2 connections.</p>
<p class="toc_element">
+ <code><a href="#fetchProcessorTypes">fetchProcessorTypes(parent, x__xgafv=None)</a></code></p>
+<p class="firstline">Fetches processor types.</p>
+<p class="toc_element">
<code><a href="#get">get(name, x__xgafv=None)</a></code></p>
<p class="firstline">Gets information about a location.</p>
<p class="toc_element">
@@ -103,6 +106,56 @@
</div>
<div class="method">
+ <code class="details" id="fetchProcessorTypes">fetchProcessorTypes(parent, x__xgafv=None)</code>
+ <pre>Fetches processor types.
+
+Args:
+ parent: string, Required. The project of processor type to list. The available processor types may depend on the whitelisting on projects. Format: projects/{project}/locations/{location} (required)
+ x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
+
+Returns:
+ An object of the form:
+
+ { # Response message for fetch processor types.
+ "processorTypes": [ # The list of processor types.
+ { # A processor type is responsible for performing a certain document understanding task on a certain type of document. All processor types are created by the documentai service internally. User will only list all available processor types via UI. For different users (projects), the available processor types may be different since we'll expose the access of some types via EAP whitelisting. We make the ProcessorType a resource under location so we have a unified API and keep the possibility that UI will load different available processor types from different regions. But for alpha the behavior is that the user will always get the union of all available processor types among all regions no matter which regionalized endpoint is called, and then we use the 'available_locations' field to show under which regions a processor type is available. For example, users can call either the 'US' or 'EU' endpoint to feach processor types. In the return, we will have an 'invoice parsing' processor with 'available_locations' field only containing 'US'. So the user can try to create an 'invoice parsing' processor under the location 'US'. Such attempt of creating under the location 'EU' will fail. Next ID: 7.
+ "allowCreation": True or False, # Whether the processor type allows creation. If yes, user can create a processor of this processor type. Otherwise, user needs to require for whitelisting.
+ "availableLocations": [ # The locations in which this processor is available.
+ { # The location information about where the processor is available.
+ "locationId": "A String", # The location id, currently must be one of [us, eu].
+ },
+ ],
+ "category": "A String", # The processor category, used by UI to group processor types.
+ "name": "A String", # The resource name of the processor type. Format: projects/{project}/processorTypes/{processor_type}
+ "schema": { # The schema defines the output of the processed document by a processor. # The schema of the default version of this processor type.
+ "description": "A String", # Description of the schema.
+ "displayName": "A String", # Display name to show to users.
+ "entityTypes": [ # Entity types of the schema.
+ { # EntityType is the wrapper of a label of the corresponding model with detailed attributes and limitations for entity-based processors. Multiple types can also compose a dependency tree to represent nested types.
+ "baseType": "A String", # Type of the entity. It must be one of the following: `document` - the entity represents a classification of a logical document. `object` - if the entity has properties it is likely an object (or or a document.) `datetime` - the entity is a date or time value. `money` - the entity represents a money value amount. `number` - the entity is a number - integer or floating point. `string` - the entity is a string value. `boolean` - the entity is a boolean value. `address` - the entity is a location address.
+ "description": "A String", # Description of the entity type.
+ "enumValues": [ # For some entity types there are only a few possible values. They can be specified here.
+ "A String",
+ ],
+ "occurrenceType": "A String", # Occurrence type limits the number of times an entity type appears in the document.
+ "properties": [ # Describing the nested structure of an entity. An EntityType may consist of several other EntityTypes. For example, in a document there can be an EntityType 'ID', which consists of EntityType 'name' and 'address', with corresponding attributes, such as TEXT for both types and ONCE for occurrence types.
+ # Object with schema name: GoogleCloudDocumentaiV1beta3SchemaEntityType
+ ],
+ "source": "A String", # Source of this entity type.
+ "type": "A String", # Name of the type. It must be unique within the set of same level types.
+ },
+ ],
+ },
+ "type": "A String", # The type of the processor, e.g, "invoice_parsing".
+ },
+ ],
+}</pre>
+</div>
+
+<div class="method">
<code class="details" id="get">get(name, x__xgafv=None)</code>
<pre>Gets information about a location.