Update documentation

google_drive2_cli/permissions_insert/index.html

@@ -5,7 +5,7 @@
   <meta charset="utf-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   
-  <title>Insert - drive v2.0.4+20210322</title>
+  <title>Insert - drive v3.0.0+20220225</title>
   
 
   
@@ -34,7 +34,7 @@
     
     <nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
       <div class="wy-side-nav-search">
-        <a href=".." class="icon icon-home"> drive v2.0.4+20210322</a>
+        <a href=".." class="icon icon-home"> drive v3.0.0+20220225</a>
         
       </div>
 
@@ -573,6 +573,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
   id: string
   kind: string
   name: string
+  pending-owner: boolean
   photo-link: string
   role: string
   self-link: string
@@ -585,32 +586,32 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 
 <p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
 <ul>
-<li><code>-r .    additional-roles=sanctus</code><ul>
+<li><code>-r .    additional-roles=invidunt</code><ul>
 <li>Additional roles for this user. Only commenter is currently allowed, though more may be supported in the future.</li>
 <li>Each invocation of this argument appends the given value to the array.</li>
 </ul>
 </li>
-<li><code>auth-key=dolor</code><ul>
+<li><code>auth-key=dolore</code><ul>
 <li>Deprecated.</li>
 </ul>
 </li>
-<li><code>deleted=true</code><ul>
+<li><code>deleted=false</code><ul>
 <li>Whether the account associated with this permission has been deleted. This field only pertains to user and group permissions.</li>
 </ul>
 </li>
-<li><code>domain=est</code><ul>
+<li><code>domain=nonumy</code><ul>
 <li>The domain name of the entity this permission refers to. This is an output-only field which is present when the permission type is user, group or domain.</li>
 </ul>
 </li>
-<li><code>email-address=nonumy</code><ul>
+<li><code>email-address=labore</code><ul>
 <li>The email address of the user or group this permission refers to. This is an output-only field which is present when the permission type is user or group.</li>
 </ul>
 </li>
-<li><code>etag=duo</code><ul>
+<li><code>etag=et</code><ul>
 <li>The ETag of the permission.</li>
 </ul>
 </li>
-<li><code>expiration-date=sed</code><ul>
+<li><code>expiration-date=et</code><ul>
 <li>The time at which this permission will expire (RFC 3339 date-time). Expiration dates have the following restrictions:  <ul>
 <li>They cannot be set on shared drive items </li>
 <li>They can only be set on user and group permissions </li>
@@ -621,23 +622,27 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </li>
 </ul>
 </li>
-<li><code>id=invidunt</code><ul>
+<li><code>id=nonumy</code><ul>
 <li>The ID of the user this permission refers to, and identical to the permissionId in the About and Files resources. When making a drive.permissions.insert request, exactly one of the id or value fields must be specified unless the permission type is anyone, in which case both id and value are ignored.</li>
 </ul>
 </li>
-<li><code>kind=takimata</code><ul>
+<li><code>kind=sit</code><ul>
 <li>This is always drive#permission.</li>
 </ul>
 </li>
-<li><code>name=et</code><ul>
+<li><code>name=lorem</code><ul>
 <li>The name for this permission.</li>
 </ul>
 </li>
-<li><code>photo-link=tempor</code><ul>
+<li><code>pending-owner=true</code><ul>
+<li>Whether the account associated with this permission is a pending owner. Only populated for user type permissions for files that are not in a shared drive.</li>
+</ul>
+</li>
+<li><code>photo-link=sea</code><ul>
 <li>A link to the profile photo, if available.</li>
 </ul>
 </li>
-<li><code>role=nonumy</code><ul>
+<li><code>role=duo</code><ul>
 <li>The primary role for this user. While new values may be supported in the future, the following are currently allowed:  <ul>
 <li>owner </li>
 <li>organizer </li>
@@ -648,11 +653,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </li>
 </ul>
 </li>
-<li><code>self-link=sanctus</code><ul>
+<li><code>self-link=sea</code><ul>
 <li>A link back to this permission.</li>
 </ul>
 </li>
-<li><code>type=labore</code><ul>
+<li><code>type=stet</code><ul>
 <li>The account type. Allowed values are:  <ul>
 <li>user </li>
 <li>group </li>
@@ -662,15 +667,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </li>
 </ul>
 </li>
-<li><code>value=est</code><ul>
+<li><code>value=erat</code><ul>
 <li>The email address or domain name for the entity. This is used during inserts and is not populated in responses. When making a drive.permissions.insert request, exactly one of the id or value fields must be specified unless the permission type is anyone, in which case both id and value are ignored.</li>
 </ul>
 </li>
-<li><code>view=sadipscing</code><ul>
+<li><code>view=eirmod</code><ul>
 <li>Indicates the view for this permission. Only populated for permissions that belong to a view. published is the only supported value.</li>
 </ul>
 </li>
-<li><code>with-link=false</code><ul>
+<li><code>with-link=true</code><ul>
 <li>Whether the link is required for this permission.</li>
 </ul>
 </li>