Update documentation

google_drive3_cli/permissions_create/index.html

@@ -5,7 +5,7 @@
   <meta charset="utf-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   
-  <title>Create - drive v2.0.4+20210322</title>
+  <title>Create - 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>
 
@@ -417,6 +417,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
   expiration-time: string
   id: string
   kind: string
+  pending-owner: boolean
   photo-link: string
   role: string
   type: string
@@ -426,7 +427,7 @@ 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 .    allow-file-discovery=false</code><ul>
+<li><code>-r .    allow-file-discovery=true</code><ul>
 <li>Whether the permission allows the file to be discovered through search. This is only applicable for permissions of type domain or anyone.</li>
 </ul>
 </li>
@@ -434,7 +435,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 <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>display-name=dolor</code><ul>
+<li><code>display-name=elitr</code><ul>
 <li>The &#34;pretty&#34; name of the value of the permission. The following is a list of examples for each type of permission:  <ul>
 <li>user - User&#39;s full name, as defined for their Google account, such as &#34;Joe Smith.&#34; </li>
 <li>group - Name of the Google Group, such as &#34;The Company Administrators.&#34; </li>
@@ -444,15 +445,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </li>
 </ul>
 </li>
-<li><code>domain=duo</code><ul>
+<li><code>domain=diam</code><ul>
 <li>The domain to which this permission refers.</li>
 </ul>
 </li>
-<li><code>email-address=diam</code><ul>
+<li><code>email-address=sed</code><ul>
 <li>The email address of the user or group to which this permission refers.</li>
 </ul>
 </li>
-<li><code>expiration-time=et</code><ul>
+<li><code>expiration-time=lorem</code><ul>
 <li>The time at which this permission will expire (RFC 3339 date-time). Expiration times have the following restrictions:  <ul>
 <li>They can only be set on user and group permissions </li>
 <li>The time must be in the future </li>
@@ -461,19 +462,23 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </li>
 </ul>
 </li>
-<li><code>id=lorem</code><ul>
+<li><code>id=magna</code><ul>
 <li>The ID of this permission. This is a unique identifier for the grantee, and is published in User resources as permissionId. IDs should be treated as opaque values.</li>
 </ul>
 </li>
-<li><code>kind=no</code><ul>
+<li><code>kind=duo</code><ul>
 <li>Identifies what kind of resource this is. Value: the fixed string &#34;drive#permission&#34;.</li>
 </ul>
 </li>
-<li><code>photo-link=sea</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=no</code><ul>
 <li>A link to the user&#39;s profile photo, if available.</li>
 </ul>
 </li>
-<li><code>role=et</code><ul>
+<li><code>role=sadipscing</code><ul>
 <li>The role granted by this permission. While new values may be supported in the future, the following are currently allowed:  <ul>
 <li>owner </li>
 <li>organizer </li>
@@ -485,7 +490,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </li>
 </ul>
 </li>
-<li><code>type=voluptua.</code><ul>
+<li><code>type=sit</code><ul>
 <li>The type of the grantee. Valid values are:  <ul>
 <li>user </li>
 <li>group </li>
@@ -495,7 +500,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </li>
 </ul>
 </li>
-<li><code>view=ipsum</code><ul>
+<li><code>view=duo</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>
@@ -563,7 +568,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
 <li>
 <p><strong>-p transfer-ownership=boolean</strong></p>
 <ul>
-<li>Whether to transfer ownership to the specified user and downgrade the current owner to a writer. This parameter is required as an acknowledgement of the side effect.</li>
+<li>Whether to transfer ownership to the specified user and downgrade the current owner to a writer. This parameter is required as an acknowledgement of the side effect. File owners can only transfer ownership of files existing on My Drive. Files existing in a shared drive are owned by the organization that owns that shared drive. Ownership transfers are not supported for files and folders in shared drives. Organizers of a shared drive can move items from that shared drive into their My Drive which transfers the ownership to them.</li>
 </ul>
 </li>
 <li>