Update documentation

google_servicedirectory1_beta1_cli/projects_locations-namespaces-services-create/index.html

@@ -5,7 +5,7 @@
   <meta charset="utf-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   
-  <title>Locations Namespaces Services Create - Service Directory v2.0.4+20210316</title>
+  <title>Locations Namespaces Services Create - Service Directory v3.0.0+20220224</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"> Service Directory v2.0.4+20210316</a>
+        <a href=".." class="icon icon-home"> Service Directory v3.0.0+20220224</a>
         
       </div>
 
@@ -241,22 +241,32 @@ You can set the scope for this method like this: <code>servicedirectory1-beta1 -
 In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.</p>
 <p>For example, a structure like this:</p>
 <pre><code>Service:
+  create-time: string
   metadata: { string: string }
   name: string
+  update-time: string
 
 </code></pre>
 
 <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 .    metadata=key=at</code><ul>
-<li>Optional. Metadata for the service. This data can be consumed by service clients. Restrictions: * The entire metadata dictionary may contain up to 2000 characters, spread accoss all key-value pairs. Metadata that goes beyond this limit are rejected * Valid metadata keys have two segments: an optional prefix and name, separated by a slash (/). The name segment is required and must be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), underscores (_), dots (.), and alphanumerics between. The prefix is optional. If specified, the prefix must be a DNS subdomain: a series of DNS labels separated by dots (.), not longer than 253 characters in total, followed by a slash (/). Metadata that fails to meet these requirements are rejected * The <code>(*.)google.com/</code> and <code>(*.)googleapis.com/</code> prefixes are reserved for system metadata managed by Service Directory. If the user tries to write to these keyspaces, those entries are silently ignored by the system Note: This field is equivalent to the <code>annotations</code> field in the v1 API. They have the same syntax and read/write to the same location in Service Directory.</li>
+<li><code>-r .    create-time=takimata</code><ul>
+<li>Output only. The timestamp when the service was created.</li>
+</ul>
+</li>
+<li><code>metadata=key=amet.</code><ul>
+<li>Optional. Metadata for the service. This data can be consumed by service clients. Restrictions: * The entire metadata dictionary may contain up to 2000 characters, spread accoss all key-value pairs. Metadata that goes beyond this limit are rejected * Valid metadata keys have two segments: an optional prefix and name, separated by a slash (/). The name segment is required and must be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), underscores (_), dots (.), and alphanumerics between. The prefix is optional. If specified, the prefix must be a DNS subdomain: a series of DNS labels separated by dots (.), not longer than 253 characters in total, followed by a slash (/). Metadata that fails to meet these requirements are rejected Note: This field is equivalent to the <code>annotations</code> field in the v1 API. They have the same syntax and read/write to the same location in Service Directory.</li>
 <li>the value will be associated with the given <code>key</code></li>
 </ul>
 </li>
-<li><code>name=sanctus</code><ul>
+<li><code>name=duo</code><ul>
 <li>Immutable. The resource name for the service in the format <code>projects/*/locations/*/namespaces/*/services/*</code>.</li>
 </ul>
 </li>
+<li><code>update-time=ipsum</code><ul>
+<li>Output only. The timestamp when the service was last updated. Note: endpoints being created/deleted/updated within the service are not considered service updates for the purpose of this timestamp.</li>
+</ul>
+</li>
 </ul>
 <h3 id="about-cursors">About Cursors</h3>
 <p>The cursor position is key to comfortably set complex nested structures. The following rules apply:</p>