Regen docs (#364)
diff --git a/docs/dyn/androidenterprise_v1.enterprises.html b/docs/dyn/androidenterprise_v1.enterprises.html
index a31348c..78800f1 100644
--- a/docs/dyn/androidenterprise_v1.enterprises.html
+++ b/docs/dyn/androidenterprise_v1.enterprises.html
@@ -82,10 +82,10 @@
<p class="firstline">Completes the signup flow, by specifying the Completion token and Enterprise token. This request must not be called multiple times for a given Enterprise Token.</p>
<p class="toc_element">
<code><a href="#createWebToken">createWebToken(enterpriseId, body)</a></code></p>
-<p class="firstline">Returns a unique token to access an embeddable UI. To generate a web UI, pass the generated token into the Play for Work javascript API. Each token may only be used to start one UI session. See the javascript API documentation for further information.</p>
+<p class="firstline">Returns a unique token to access an embeddable UI. To generate a web UI, pass the generated token into the managed Google Play javascript API. Each token may only be used to start one UI session. See the javascript API documentation for further information.</p>
<p class="toc_element">
<code><a href="#delete">delete(enterpriseId)</a></code></p>
-<p class="firstline">Deletes the binding between the EMM and enterprise. This is now deprecated; use this to unenroll customers that were previously enrolled with the 'insert' call, then enroll them again with the 'enroll' call.</p>
+<p class="firstline">Deletes the binding between the EMM and enterprise. This is now deprecated. Use this method only to unenroll customers that were previously enrolled with the insert call, then enroll them again with the enroll call.</p>
<p class="toc_element">
<code><a href="#enroll">enroll(token, body)</a></code></p>
<p class="firstline">Enrolls an enterprise with the calling EMM.</p>
@@ -115,10 +115,10 @@
<p class="firstline">Sends a test push notification to validate the EMM integration with the Google Cloud Pub/Sub service for this enterprise.</p>
<p class="toc_element">
<code><a href="#setAccount">setAccount(enterpriseId, body)</a></code></p>
-<p class="firstline">Set the account that will be used to authenticate to the API as the enterprise.</p>
+<p class="firstline">Sets the account that will be used to authenticate to the API as the enterprise.</p>
<p class="toc_element">
<code><a href="#setStoreLayout">setStoreLayout(enterpriseId, body)</a></code></p>
-<p class="firstline">Sets the store layout for the enterprise. By default, storeLayoutType is set to "basic" and the basic store layout is enabled. The basic layout only contains apps approved by the administrator, and that have been added to the available product set for a user (using the setAvailableProductSet call). Apps on the page are sorted in order of their product ID value. If you create a custom store layout (by setting storeLayoutType = "custom"), the basic store layout is disabled.</p>
+<p class="firstline">Sets the store layout for the enterprise. By default, storeLayoutType is set to "basic" and the basic store layout is enabled. The basic layout only contains apps approved by the admin, and that have been added to the available product set for a user (using the setAvailableProductSet call). Apps on the page are sorted in order of their product ID value. If you create a custom store layout (by setting storeLayoutType = "custom"), the basic store layout is disabled.</p>
<p class="toc_element">
<code><a href="#unenroll">unenroll(enterpriseId)</a></code></p>
<p class="firstline">Unenrolls an enterprise from the calling EMM.</p>
@@ -145,10 +145,10 @@
{ # An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows:
# - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process.
- # - For Android for Work Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the Android for Work Sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
- "administrator": [ # Administrators of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
- { # This represents an enterprise administrator who can manage the enterprise in the Google Play for Work Store.
- "email": "A String", # The administrator's email address.
+ # - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
+ "administrator": [ # Admins of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
+ { # This represents an enterprise admin who can manage the enterprise in the managed Google Play store.
+ "email": "A String", # The admin's email address.
},
],
"primaryDomain": "A String", # The enterprise's primary domain, such as "example.com".
@@ -160,7 +160,7 @@
<div class="method">
<code class="details" id="createWebToken">createWebToken(enterpriseId, body)</code>
- <pre>Returns a unique token to access an embeddable UI. To generate a web UI, pass the generated token into the Play for Work javascript API. Each token may only be used to start one UI session. See the javascript API documentation for further information.
+ <pre>Returns a unique token to access an embeddable UI. To generate a web UI, pass the generated token into the managed Google Play javascript API. Each token may only be used to start one UI session. See the javascript API documentation for further information.
Args:
enterpriseId: string, The ID of the enterprise. (required)
@@ -179,7 +179,7 @@
Returns:
An object of the form:
- { # A token authorizing an administrator to access an iframe.
+ { # A token authorizing an admin to access an iframe.
"kind": "androidenterprise#administratorWebToken", # Identifies what kind of resource this is. Value: the fixed string "androidenterprise#administratorWebToken".
"token": "A String", # An opaque token to be passed to the Play front-end to generate an iframe.
}</pre>
@@ -187,7 +187,7 @@
<div class="method">
<code class="details" id="delete">delete(enterpriseId)</code>
- <pre>Deletes the binding between the EMM and enterprise. This is now deprecated; use this to unenroll customers that were previously enrolled with the 'insert' call, then enroll them again with the 'enroll' call.
+ <pre>Deletes the binding between the EMM and enterprise. This is now deprecated. Use this method only to unenroll customers that were previously enrolled with the insert call, then enroll them again with the enroll call.
Args:
enterpriseId: string, The ID of the enterprise. (required)
@@ -205,10 +205,10 @@
{ # An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows:
# - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process.
- # - For Android for Work Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the Android for Work Sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
- "administrator": [ # Administrators of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
- { # This represents an enterprise administrator who can manage the enterprise in the Google Play for Work Store.
- "email": "A String", # The administrator's email address.
+ # - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
+ "administrator": [ # Admins of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
+ { # This represents an enterprise admin who can manage the enterprise in the managed Google Play store.
+ "email": "A String", # The admin's email address.
},
],
"primaryDomain": "A String", # The enterprise's primary domain, such as "example.com".
@@ -223,10 +223,10 @@
{ # An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows:
# - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process.
- # - For Android for Work Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the Android for Work Sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
- "administrator": [ # Administrators of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
- { # This represents an enterprise administrator who can manage the enterprise in the Google Play for Work Store.
- "email": "A String", # The administrator's email address.
+ # - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
+ "administrator": [ # Admins of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
+ { # This represents an enterprise admin who can manage the enterprise in the managed Google Play store.
+ "email": "A String", # The admin's email address.
},
],
"primaryDomain": "A String", # The enterprise's primary domain, such as "example.com".
@@ -266,10 +266,10 @@
{ # An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows:
# - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process.
- # - For Android for Work Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the Android for Work Sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
- "administrator": [ # Administrators of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
- { # This represents an enterprise administrator who can manage the enterprise in the Google Play for Work Store.
- "email": "A String", # The administrator's email address.
+ # - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
+ "administrator": [ # Admins of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
+ { # This represents an enterprise admin who can manage the enterprise in the managed Google Play store.
+ "email": "A String", # The admin's email address.
},
],
"primaryDomain": "A String", # The enterprise's primary domain, such as "example.com".
@@ -322,8 +322,8 @@
Returns:
An object of the form:
- { # General setting for the Google Play for Work store layout, currently only specifying the page to display the first time the store is opened.
- "homepageId": "A String", # The ID of the store page to be used as the homepage. The homepage will be used as the first page shown in the Google Play for Work store.
+ { # General setting for the managed Google Play store layout, currently only specifying the page to display the first time the store is opened.
+ "homepageId": "A String", # The ID of the store page to be used as the homepage. The homepage will be used as the first page shown in the managed Google Play store.
#
# If a homepage has not been set, the Play store shown on devices will be empty. Not specifying a homepage on a store layout effectively empties the store.
#
@@ -344,10 +344,10 @@
{ # An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows:
# - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process.
- # - For Android for Work Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the Android for Work Sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
- "administrator": [ # Administrators of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
- { # This represents an enterprise administrator who can manage the enterprise in the Google Play for Work Store.
- "email": "A String", # The administrator's email address.
+ # - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
+ "administrator": [ # Admins of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
+ { # This represents an enterprise admin who can manage the enterprise in the managed Google Play store.
+ "email": "A String", # The admin's email address.
},
],
"primaryDomain": "A String", # The enterprise's primary domain, such as "example.com".
@@ -362,10 +362,10 @@
{ # An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows:
# - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process.
- # - For Android for Work Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the Android for Work Sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
- "administrator": [ # Administrators of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
- { # This represents an enterprise administrator who can manage the enterprise in the Google Play for Work Store.
- "email": "A String", # The administrator's email address.
+ # - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
+ "administrator": [ # Admins of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
+ { # This represents an enterprise admin who can manage the enterprise in the managed Google Play store.
+ "email": "A String", # The admin's email address.
},
],
"primaryDomain": "A String", # The enterprise's primary domain, such as "example.com".
@@ -390,10 +390,10 @@
"enterprise": [ # An enterprise.
{ # An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows:
# - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process.
- # - For Android for Work Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the Android for Work Sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
- "administrator": [ # Administrators of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
- { # This represents an enterprise administrator who can manage the enterprise in the Google Play for Work Store.
- "email": "A String", # The administrator's email address.
+ # - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.
+ "administrator": [ # Admins of the enterprise. This is only supported for enterprises created via the EMM-initiated flow.
+ { # This represents an enterprise admin who can manage the enterprise in the managed Google Play store.
+ "email": "A String", # The admin's email address.
},
],
"primaryDomain": "A String", # The enterprise's primary domain, such as "example.com".
@@ -408,7 +408,7 @@
<div class="method">
<code class="details" id="pullNotificationSet">pullNotificationSet(requestMode=None)</code>
<pre>Pulls and returns a notification set for the enterprises associated with the service account authenticated for the request. The notification set may be empty if no notification are pending.
-A notification set returned needs to be acknowledged within 20 seconds by calling Enterprises​.AcknowledgeNotificationSet, unless the notification set is empty.
+A notification set returned needs to be acknowledged within 20 seconds by calling Enterprises.AcknowledgeNotificationSet, unless the notification set is empty.
Notifications that are not acknowledged within the 20 seconds will eventually be included again in the response to another PullNotificationSet request, and those that are never acknowledged will ultimately be deleted according to the Google Cloud Platform Pub/Sub system policy.
Multiple requests might be performed concurrently to retrieve notifications, in which case the pending notifications (if any) will be split among each caller, if any are pending.
If no notifications are present, an empty notification list is returned. Subsequent requests may return more notifications once they become available.
@@ -449,6 +449,15 @@
"productId": "A String", # The id of the product (e.g. "app:com.google.android.gm") for which the approval status has changed. This field will always be present.
},
"enterpriseId": "A String", # The ID of the enterprise for which the notification is sent. This will always be present.
+ "newDeviceEvent": { # An event generated when a new device is ready to be managed. # Notifications about new devices.
+ "userId": "A String", # The ID of the user. This field will always be present.
+ "deviceId": "A String", # The Android ID of the device. This field will always be present.
+ "managementType": "A String", # Identifies the extent to which the device is controlled by an Android EMM in various deployment configurations.
+ #
+ # Possible values include:
+ # - "managedDevice", a device where the DPC is set as device owner,
+ # - "managedProfile", a device where the DPC is set as profile owner.
+ },
"installFailureEvent": { # An event generated when an app installation failed on a device # Notifications about an app installation failure.
"productId": "A String", # The id of the product (e.g. "app:com.google.android.gm") for which the install failure event occured. This field will always be present.
"userId": "A String", # The ID of the user. This field will always be present.
@@ -485,7 +494,7 @@
<div class="method">
<code class="details" id="setAccount">setAccount(enterpriseId, body)</code>
- <pre>Set the account that will be used to authenticate to the API as the enterprise.
+ <pre>Sets the account that will be used to authenticate to the API as the enterprise.
Args:
enterpriseId: string, The ID of the enterprise. (required)
@@ -509,15 +518,15 @@
<div class="method">
<code class="details" id="setStoreLayout">setStoreLayout(enterpriseId, body)</code>
- <pre>Sets the store layout for the enterprise. By default, storeLayoutType is set to "basic" and the basic store layout is enabled. The basic layout only contains apps approved by the administrator, and that have been added to the available product set for a user (using the setAvailableProductSet call). Apps on the page are sorted in order of their product ID value. If you create a custom store layout (by setting storeLayoutType = "custom"), the basic store layout is disabled.
+ <pre>Sets the store layout for the enterprise. By default, storeLayoutType is set to "basic" and the basic store layout is enabled. The basic layout only contains apps approved by the admin, and that have been added to the available product set for a user (using the setAvailableProductSet call). Apps on the page are sorted in order of their product ID value. If you create a custom store layout (by setting storeLayoutType = "custom"), the basic store layout is disabled.
Args:
enterpriseId: string, The ID of the enterprise. (required)
body: object, The request body. (required)
The object takes the form of:
-{ # General setting for the Google Play for Work store layout, currently only specifying the page to display the first time the store is opened.
- "homepageId": "A String", # The ID of the store page to be used as the homepage. The homepage will be used as the first page shown in the Google Play for Work store.
+{ # General setting for the managed Google Play store layout, currently only specifying the page to display the first time the store is opened.
+ "homepageId": "A String", # The ID of the store page to be used as the homepage. The homepage will be used as the first page shown in the managed Google Play store.
#
# If a homepage has not been set, the Play store shown on devices will be empty. Not specifying a homepage on a store layout effectively empties the store.
#
@@ -530,8 +539,8 @@
Returns:
An object of the form:
- { # General setting for the Google Play for Work store layout, currently only specifying the page to display the first time the store is opened.
- "homepageId": "A String", # The ID of the store page to be used as the homepage. The homepage will be used as the first page shown in the Google Play for Work store.
+ { # General setting for the managed Google Play store layout, currently only specifying the page to display the first time the store is opened.
+ "homepageId": "A String", # The ID of the store page to be used as the homepage. The homepage will be used as the first page shown in the managed Google Play store.
#
# If a homepage has not been set, the Play store shown on devices will be empty. Not specifying a homepage on a store layout effectively empties the store.
#