docs: update docs/dyn (#1096)

This PR was generated using Autosynth. :rainbow:

Synth log will be available here:
https://source.cloud.google.com/results/invocations/6f0f288a-a1e8-4b2d-a85f-00b1c6150185/targets

- [ ] To automatically regenerate this PR, check this box.

Source-Link: https://github.com/googleapis/synthtool/commit/39b7149da4026765385403632db3c6f63db96b2c
Source-Link: https://github.com/googleapis/synthtool/commit/9a7d9fbb7045c34c9d3d22c1ff766eeae51f04c9
Source-Link: https://github.com/googleapis/synthtool/commit/dc9903a8c30c3662b6098f0e4a97f221d67268b2
Source-Link: https://github.com/googleapis/synthtool/commit/7fcc405a579d5d53a726ff3da1b7c8c08f0f2d58
Source-Link: https://github.com/googleapis/synthtool/commit/d5fc0bcf9ea9789c5b0e3154a9e3b29e5cea6116
Source-Link: https://github.com/googleapis/synthtool/commit/e89175cf074dccc4babb4eca66ae913696e47a71
Source-Link: https://github.com/googleapis/synthtool/commit/7d652819519dfa24da9e14548232e4aaba71a11c
Source-Link: https://github.com/googleapis/synthtool/commit/7db8a6c5ffb12a6e4c2f799c18f00f7f3d60e279
Source-Link: https://github.com/googleapis/synthtool/commit/1f1148d3c7a7a52f0c98077f976bd9b3c948ee2b
Source-Link: https://github.com/googleapis/synthtool/commit/2c8aecedd55b0480fb4e123b6e07fa5b12953862
Source-Link: https://github.com/googleapis/synthtool/commit/3d3e94c4e02370f307a9a200b0c743c3d8d19f29
Source-Link: https://github.com/googleapis/synthtool/commit/c7824ea48ff6d4d42dfae0849aec8a85acd90bd9
Source-Link: https://github.com/googleapis/synthtool/commit/ba9918cd22874245b55734f57470c719b577e591
Source-Link: https://github.com/googleapis/synthtool/commit/b19b401571e77192f8dd38eab5fb2300a0de9324
Source-Link: https://github.com/googleapis/synthtool/commit/6542bd723403513626f61642fc02ddca528409aa
diff --git a/docs/dyn/pubsub_v1beta1a.subscriptions.html b/docs/dyn/pubsub_v1beta1a.subscriptions.html
index 30d4fad..c0d3007 100644
--- a/docs/dyn/pubsub_v1beta1a.subscriptions.html
+++ b/docs/dyn/pubsub_v1beta1a.subscriptions.html
@@ -90,7 +90,7 @@
   <code><a href="#get">get(subscription, x__xgafv=None)</a></code></p>
 <p class="firstline">Gets the configuration details of a subscription.</p>
 <p class="toc_element">
-  <code><a href="#list">list(query=None, pageToken=None, maxResults=None, x__xgafv=None)</a></code></p>
+  <code><a href="#list">list(pageToken=None, query=None, maxResults=None, x__xgafv=None)</a></code></p>
 <p class="firstline">Lists matching subscriptions.</p>
 <p class="toc_element">
   <code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
@@ -149,13 +149,13 @@
     The object takes the form of:
 
 { # A subscription resource.
-  &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
-  &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
-    &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
-  },
-  &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
-  &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
-}
+    &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
+      &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
+    },
+    &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
+    &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
+    &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
+  }
 
   x__xgafv: string, V1 error format.
     Allowed values
@@ -166,13 +166,13 @@
   An object of the form:
 
     { # A subscription resource.
-    &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
-    &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
-      &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
-    },
-    &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
-    &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
-  }</pre>
+      &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
+        &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
+      },
+      &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
+      &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
+      &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
+    }</pre>
 </div>
 
 <div class="method">
@@ -208,22 +208,22 @@
   An object of the form:
 
     { # A subscription resource.
-    &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
-    &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
-      &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
-    },
-    &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
-    &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
-  }</pre>
+      &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
+        &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
+      },
+      &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
+      &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
+      &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
+    }</pre>
 </div>
 
 <div class="method">
-    <code class="details" id="list">list(query=None, pageToken=None, maxResults=None, x__xgafv=None)</code>
+    <code class="details" id="list">list(pageToken=None, query=None, maxResults=None, x__xgafv=None)</code>
   <pre>Lists matching subscriptions.
 
 Args:
-  query: string, A valid label query expression.
   pageToken: string, The value obtained in the last ListSubscriptionsResponse for continuation.
+  query: string, A valid label query expression.
   maxResults: integer, Maximum number of subscriptions to return.
   x__xgafv: string, V1 error format.
     Allowed values
@@ -237,13 +237,13 @@
     &quot;nextPageToken&quot;: &quot;A String&quot;, # If not empty, indicates that there are more subscriptions that match the request and this value should be passed to the next ListSubscriptionsRequest to continue.
     &quot;subscription&quot;: [ # The subscriptions that match the request.
       { # A subscription resource.
-        &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
-        &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
-          &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
+          &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # If push delivery is used with this subscription, this field is used to configure it.
+            &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
+          },
+          &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
+          &quot;ackDeadlineSeconds&quot;: 42, # For either push or pull delivery, the value is the maximum time after a subscriber receives a message before the subscriber should acknowledge or Nack the message. If the Ack deadline for a message passes without an Ack or a Nack, the Pub/Sub system will eventually redeliver the message. If a subscriber acknowledges after the deadline, the Pub/Sub system may accept the Ack, but it is possible that the message has been already delivered again. Multiple Acks to the message are allowed and will succeed. For push delivery, this value is used to set the request timeout for the call to the push endpoint. For pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for each message using its corresponding ack_id with ModifyAckDeadline. While a message is outstanding (i.e. it has been delivered to a pull subscriber and the subscriber has not yet Acked or Nacked), the Pub/Sub system will not deliver that message to another pull subscriber (on a best-effort basis).
+          &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
         },
-        &quot;topic&quot;: &quot;A String&quot;, # The name of the topic from which this subscription is receiving messages.
-        &quot;name&quot;: &quot;A String&quot;, # Name of the subscription.
-      },
     ],
   }</pre>
 </div>
@@ -271,12 +271,12 @@
     The object takes the form of:
 
 { # Request for the ModifyAckDeadline method.
-    &quot;ackId&quot;: &quot;A String&quot;, # The acknowledgment ID. Either this or ack_ids must be populated, not both.
     &quot;ackDeadlineSeconds&quot;: 42, # The new ack deadline with respect to the time this request was sent to the Pub/Sub system. Must be &gt;= 0. For example, if the value is 10, the new ack deadline will expire 10 seconds after the ModifyAckDeadline call was made. Specifying zero may immediately make the message available for another pull request.
+    &quot;ackId&quot;: &quot;A String&quot;, # The acknowledgment ID. Either this or ack_ids must be populated, not both.
+    &quot;subscription&quot;: &quot;A String&quot;, # Next Index: 5 The name of the subscription from which messages are being pulled.
     &quot;ackIds&quot;: [ # List of acknowledgment IDs. Either this field or ack_id should be populated, not both.
       &quot;A String&quot;,
     ],
-    &quot;subscription&quot;: &quot;A String&quot;, # Next Index: 5 The name of the subscription from which messages are being pulled.
   }
 
   x__xgafv: string, V1 error format.
@@ -300,10 +300,10 @@
     The object takes the form of:
 
 { # Request for the ModifyPushConfig method.
+    &quot;subscription&quot;: &quot;A String&quot;, # The name of the subscription.
     &quot;pushConfig&quot;: { # Configuration for a push delivery endpoint. # An empty push_config indicates that the Pub/Sub system should pause pushing messages from the given subscription.
       &quot;pushEndpoint&quot;: &quot;A String&quot;, # A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use &quot;https://example.com/push&quot;.
     },
-    &quot;subscription&quot;: &quot;A String&quot;, # The name of the subscription.
   }
 
   x__xgafv: string, V1 error format.
@@ -327,8 +327,8 @@
     The object takes the form of:
 
 { # Request for the Pull method.
-    &quot;returnImmediately&quot;: True or False, # If this is specified as true the system will respond immediately even if it is not able to return a message in the Pull response. Otherwise the system is allowed to wait until at least one message is available rather than returning FAILED_PRECONDITION. The client may cancel the request if it does not wish to wait any longer for the response.
     &quot;subscription&quot;: &quot;A String&quot;, # The subscription from which a message should be pulled.
+    &quot;returnImmediately&quot;: True or False, # If this is specified as true the system will respond immediately even if it is not able to return a message in the Pull response. Otherwise the system is allowed to wait until at least one message is available rather than returning FAILED_PRECONDITION. The client may cancel the request if it does not wish to wait any longer for the response.
   }
 
   x__xgafv: string, V1 error format.
@@ -342,21 +342,21 @@
     { # Either a PubsubMessage or a truncation event. One of these two must be populated.
     &quot;ackId&quot;: &quot;A String&quot;, # This ID must be used to acknowledge the received event or message.
     &quot;pubsubEvent&quot;: { # An event indicating a received message or truncation event. # A pubsub message or truncation event.
+      &quot;truncated&quot;: True or False, # Indicates that this subscription has been truncated.
+      &quot;subscription&quot;: &quot;A String&quot;, # The subscription that received the event.
+      &quot;deleted&quot;: True or False, # Indicates that this subscription has been deleted. (Note that pull subscribers will always receive NOT_FOUND in response in their pull request on the subscription, rather than seeing this boolean.)
       &quot;message&quot;: { # A message data and its labels. # A received message.
-        &quot;messageId&quot;: &quot;A String&quot;, # ID of this message assigned by the server at publication time. Guaranteed to be unique within the topic. This value may be read by a subscriber that receives a PubsubMessage via a Pull call or a push delivery. It must not be populated by a publisher in a Publish call.
         &quot;data&quot;: &quot;A String&quot;, # The message payload.
-        &quot;publishTime&quot;: &quot;A String&quot;, # The time at which the message was published. The time is milliseconds since the UNIX epoch.
         &quot;label&quot;: [ # Optional list of labels for this message. Keys in this collection must be unique.
           { # A key-value pair applied to a given object.
-            &quot;key&quot;: &quot;A String&quot;, # The key of a label is a syntactically valid URL (as per RFC 1738) with the &quot;scheme&quot; and initial slashes omitted and with the additional restrictions noted below. Each key should be globally unique. The &quot;host&quot; portion is called the &quot;namespace&quot; and is not necessarily resolvable to a network endpoint. Instead, the namespace indicates what system or entity defines the semantics of the label. Namespaces do not restrict the set of objects to which a label may be associated. Keys are defined by the following grammar: key = hostname &quot;/&quot; kpath kpath = ksegment *[ &quot;/&quot; ksegment ] ksegment = alphadigit | *[ alphadigit | &quot;-&quot; | &quot;_&quot; | &quot;.&quot; ] where &quot;hostname&quot; and &quot;alphadigit&quot; are defined as in RFC 1738. Example key: spanner.google.com/universe
             &quot;strValue&quot;: &quot;A String&quot;, # A string value.
+            &quot;key&quot;: &quot;A String&quot;, # The key of a label is a syntactically valid URL (as per RFC 1738) with the &quot;scheme&quot; and initial slashes omitted and with the additional restrictions noted below. Each key should be globally unique. The &quot;host&quot; portion is called the &quot;namespace&quot; and is not necessarily resolvable to a network endpoint. Instead, the namespace indicates what system or entity defines the semantics of the label. Namespaces do not restrict the set of objects to which a label may be associated. Keys are defined by the following grammar: key = hostname &quot;/&quot; kpath kpath = ksegment *[ &quot;/&quot; ksegment ] ksegment = alphadigit | *[ alphadigit | &quot;-&quot; | &quot;_&quot; | &quot;.&quot; ] where &quot;hostname&quot; and &quot;alphadigit&quot; are defined as in RFC 1738. Example key: spanner.google.com/universe
             &quot;numValue&quot;: &quot;A String&quot;, # An integer value.
           },
         ],
+        &quot;publishTime&quot;: &quot;A String&quot;, # The time at which the message was published. The time is milliseconds since the UNIX epoch.
+        &quot;messageId&quot;: &quot;A String&quot;, # ID of this message assigned by the server at publication time. Guaranteed to be unique within the topic. This value may be read by a subscriber that receives a PubsubMessage via a Pull call or a push delivery. It must not be populated by a publisher in a Publish call.
       },
-      &quot;subscription&quot;: &quot;A String&quot;, # The subscription that received the event.
-      &quot;deleted&quot;: True or False, # Indicates that this subscription has been deleted. (Note that pull subscribers will always receive NOT_FOUND in response in their pull request on the subscription, rather than seeing this boolean.)
-      &quot;truncated&quot;: True or False, # Indicates that this subscription has been truncated.
     },
   }</pre>
 </div>
@@ -388,21 +388,21 @@
       { # Either a PubsubMessage or a truncation event. One of these two must be populated.
         &quot;ackId&quot;: &quot;A String&quot;, # This ID must be used to acknowledge the received event or message.
         &quot;pubsubEvent&quot;: { # An event indicating a received message or truncation event. # A pubsub message or truncation event.
+          &quot;truncated&quot;: True or False, # Indicates that this subscription has been truncated.
+          &quot;subscription&quot;: &quot;A String&quot;, # The subscription that received the event.
+          &quot;deleted&quot;: True or False, # Indicates that this subscription has been deleted. (Note that pull subscribers will always receive NOT_FOUND in response in their pull request on the subscription, rather than seeing this boolean.)
           &quot;message&quot;: { # A message data and its labels. # A received message.
-            &quot;messageId&quot;: &quot;A String&quot;, # ID of this message assigned by the server at publication time. Guaranteed to be unique within the topic. This value may be read by a subscriber that receives a PubsubMessage via a Pull call or a push delivery. It must not be populated by a publisher in a Publish call.
             &quot;data&quot;: &quot;A String&quot;, # The message payload.
-            &quot;publishTime&quot;: &quot;A String&quot;, # The time at which the message was published. The time is milliseconds since the UNIX epoch.
             &quot;label&quot;: [ # Optional list of labels for this message. Keys in this collection must be unique.
               { # A key-value pair applied to a given object.
-                &quot;key&quot;: &quot;A String&quot;, # The key of a label is a syntactically valid URL (as per RFC 1738) with the &quot;scheme&quot; and initial slashes omitted and with the additional restrictions noted below. Each key should be globally unique. The &quot;host&quot; portion is called the &quot;namespace&quot; and is not necessarily resolvable to a network endpoint. Instead, the namespace indicates what system or entity defines the semantics of the label. Namespaces do not restrict the set of objects to which a label may be associated. Keys are defined by the following grammar: key = hostname &quot;/&quot; kpath kpath = ksegment *[ &quot;/&quot; ksegment ] ksegment = alphadigit | *[ alphadigit | &quot;-&quot; | &quot;_&quot; | &quot;.&quot; ] where &quot;hostname&quot; and &quot;alphadigit&quot; are defined as in RFC 1738. Example key: spanner.google.com/universe
                 &quot;strValue&quot;: &quot;A String&quot;, # A string value.
+                &quot;key&quot;: &quot;A String&quot;, # The key of a label is a syntactically valid URL (as per RFC 1738) with the &quot;scheme&quot; and initial slashes omitted and with the additional restrictions noted below. Each key should be globally unique. The &quot;host&quot; portion is called the &quot;namespace&quot; and is not necessarily resolvable to a network endpoint. Instead, the namespace indicates what system or entity defines the semantics of the label. Namespaces do not restrict the set of objects to which a label may be associated. Keys are defined by the following grammar: key = hostname &quot;/&quot; kpath kpath = ksegment *[ &quot;/&quot; ksegment ] ksegment = alphadigit | *[ alphadigit | &quot;-&quot; | &quot;_&quot; | &quot;.&quot; ] where &quot;hostname&quot; and &quot;alphadigit&quot; are defined as in RFC 1738. Example key: spanner.google.com/universe
                 &quot;numValue&quot;: &quot;A String&quot;, # An integer value.
               },
             ],
+            &quot;publishTime&quot;: &quot;A String&quot;, # The time at which the message was published. The time is milliseconds since the UNIX epoch.
+            &quot;messageId&quot;: &quot;A String&quot;, # ID of this message assigned by the server at publication time. Guaranteed to be unique within the topic. This value may be read by a subscriber that receives a PubsubMessage via a Pull call or a push delivery. It must not be populated by a publisher in a Publish call.
           },
-          &quot;subscription&quot;: &quot;A String&quot;, # The subscription that received the event.
-          &quot;deleted&quot;: True or False, # Indicates that this subscription has been deleted. (Note that pull subscribers will always receive NOT_FOUND in response in their pull request on the subscription, rather than seeing this boolean.)
-          &quot;truncated&quot;: True or False, # Indicates that this subscription has been truncated.
         },
       },
     ],