Release v1.6.0 (#324)
* Update version and changelog for v1.6.0
* Update docs
diff --git a/docs/dyn/pubsub_v1beta1a.topics.html b/docs/dyn/pubsub_v1beta1a.topics.html
index 17132a6..a46385c 100644
--- a/docs/dyn/pubsub_v1beta1a.topics.html
+++ b/docs/dyn/pubsub_v1beta1a.topics.html
@@ -79,10 +79,10 @@
<p class="firstline">Creates the given topic with the given name.</p>
<p class="toc_element">
<code><a href="#delete">delete(topic, x__xgafv=None)</a></code></p>
-<p class="firstline">Deletes the topic with the given name. Returns NOT_FOUND if the topic does not exist. After a topic is deleted, a new topic may be created with the same name.</p>
+<p class="firstline">Deletes the topic with the given name. Returns NOT_FOUND if the topic does</p>
<p class="toc_element">
<code><a href="#get">get(topic, x__xgafv=None)</a></code></p>
-<p class="firstline">Gets the configuration of a topic. Since the topic only has the name attribute, this method is only useful to check the existence of a topic. If other attributes are added in the future, they will be returned here.</p>
+<p class="firstline">Gets the configuration of a topic. Since the topic only has the name</p>
<p class="toc_element">
<code><a href="#list">list(maxResults=None, pageToken=None, query=None, x__xgafv=None)</a></code></p>
<p class="firstline">Lists matching topics.</p>
@@ -91,10 +91,10 @@
<p class="firstline">Retrieves the next page of results.</p>
<p class="toc_element">
<code><a href="#publish">publish(body, x__xgafv=None)</a></code></p>
-<p class="firstline">Adds a message to the topic. Returns NOT_FOUND if the topic does not exist.</p>
+<p class="firstline">Adds a message to the topic. Returns NOT_FOUND if the topic does not</p>
<p class="toc_element">
<code><a href="#publishBatch">publishBatch(body, x__xgafv=None)</a></code></p>
-<p class="firstline">Adds one or more messages to the topic. Returns NOT_FOUND if the topic does not exist.</p>
+<p class="firstline">Adds one or more messages to the topic. Returns NOT_FOUND if the topic does</p>
<h3>Method Details</h3>
<div class="method">
<code class="details" id="create">create(body, x__xgafv=None)</code>
@@ -109,6 +109,9 @@
}
x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
Returns:
An object of the form:
@@ -120,26 +123,49 @@
<div class="method">
<code class="details" id="delete">delete(topic, x__xgafv=None)</code>
- <pre>Deletes the topic with the given name. Returns NOT_FOUND if the topic does not exist. After a topic is deleted, a new topic may be created with the same name.
+ <pre>Deletes the topic with the given name. Returns NOT_FOUND if the topic does
+not exist. After a topic is deleted, a new topic may be created with the
+same name.
Args:
topic: string, Name of the topic to delete. (required)
x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
Returns:
An object of the form:
- { # An empty message that you can re-use to avoid defining duplicated empty messages in your project. A typical example is to use it as argument or the return value of a service API. For instance: service Foo { rpc Bar (proto2.Empty) returns (proto2.Empty) { }; }; BEGIN GOOGLE-INTERNAL The difference between this one and net/rpc/empty-message.proto is that 1) The generated message here is in proto2 C++ API. 2) The proto2.Empty has minimum dependencies (no message_set or net/rpc dependencies) END GOOGLE-INTERNAL
+ { # An empty message that you can re-use to avoid defining duplicated empty
+ # messages in your project. A typical example is to use it as argument or the
+ # return value of a service API. For instance:
+ #
+ # service Foo {
+ # rpc Bar (proto2.Empty) returns (proto2.Empty) { };
+ # };
+ #
+ # BEGIN GOOGLE-INTERNAL
+ # The difference between this one and net/rpc/empty-message.proto is that
+ # 1) The generated message here is in proto2 C++ API.
+ # 2) The proto2.Empty has minimum dependencies
+ # (no message_set or net/rpc dependencies)
+ # END GOOGLE-INTERNAL
}</pre>
</div>
<div class="method">
<code class="details" id="get">get(topic, x__xgafv=None)</code>
- <pre>Gets the configuration of a topic. Since the topic only has the name attribute, this method is only useful to check the existence of a topic. If other attributes are added in the future, they will be returned here.
+ <pre>Gets the configuration of a topic. Since the topic only has the name
+attribute, this method is only useful to check the existence of a topic.
+If other attributes are added in the future, they will be returned here.
Args:
topic: string, The name of the topic to get. (required)
x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
Returns:
An object of the form:
@@ -155,9 +181,13 @@
Args:
maxResults: integer, Maximum number of topics to return.
- pageToken: string, The value obtained in the last ListTopicsResponse for continuation.
+ pageToken: string, The value obtained in the last <code>ListTopicsResponse</code>
+for continuation.
query: string, A valid label query expression.
x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
Returns:
An object of the form:
@@ -168,7 +198,9 @@
"name": "A String", # Name of the topic.
},
],
- "nextPageToken": "A String", # If not empty, indicates that there are more topics that match the request, and this value should be passed to the next ListTopicsRequest to continue.
+ "nextPageToken": "A String", # If not empty, indicates that there are more topics that match the request,
+ # and this value should be passed to the next <code>ListTopicsRequest</code>
+ # to continue.
}</pre>
</div>
@@ -188,7 +220,8 @@
<div class="method">
<code class="details" id="publish">publish(body, x__xgafv=None)</code>
- <pre>Adds a message to the topic. Returns NOT_FOUND if the topic does not exist.
+ <pre>Adds a message to the topic. Returns NOT_FOUND if the topic does not
+exist.
Args:
body: object, The request body. (required)
@@ -197,31 +230,70 @@
{ # Request for the Publish method.
"topic": "A String", # The message in the request will be published on this topic.
"message": { # A message data and its labels. # The message to publish.
- "messageId": "A String", # 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.
- "data": "A String", # The message payload.
- "publishTime": "A String", # The time at which the message was published. The time is milliseconds since the UNIX epoch.
- "label": [ # Optional list of labels for this message. Keys in this collection must be unique.
+ "label": [ # Optional list of labels for this message. Keys in this collection must
+ # be unique.
{ # A key-value pair applied to a given object.
"numValue": "A String", # An integer value.
"strValue": "A String", # A string value.
- "key": "A String", # The key of a label is a syntactically valid URL (as per RFC 1738) with the "scheme" and initial slashes omitted and with the additional restrictions noted below. Each key should be globally unique. The "host" portion is called the "namespace" 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 "/" kpath kpath = ksegment *[ "/" ksegment ] ksegment = alphadigit | *[ alphadigit | "-" | "_" | "." ] where "hostname" and "alphadigit" are defined as in RFC 1738. Example key: spanner.google.com/universe
+ "key": "A String", # The key of a label is a syntactically valid URL (as per RFC 1738) with
+ # the "scheme" and initial slashes omitted and with the additional
+ # restrictions noted below. Each key should be globally unique. The
+ # "host" portion is called the "namespace" 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 "/" kpath
+ # kpath = ksegment *[ "/" ksegment ]
+ # ksegment = alphadigit | *[ alphadigit | "-" | "_" | "." ]
+ #
+ # where "hostname" and "alphadigit" are defined as in RFC 1738.
+ #
+ # Example key:
+ # spanner.google.com/universe
},
],
+ "data": "A String", # The message payload.
+ "publishTime": "A String", # The time at which the message was published.
+ # The time is milliseconds since the UNIX epoch.
+ "messageId": "A String", # 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.
},
}
x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
Returns:
An object of the form:
- { # An empty message that you can re-use to avoid defining duplicated empty messages in your project. A typical example is to use it as argument or the return value of a service API. For instance: service Foo { rpc Bar (proto2.Empty) returns (proto2.Empty) { }; }; BEGIN GOOGLE-INTERNAL The difference between this one and net/rpc/empty-message.proto is that 1) The generated message here is in proto2 C++ API. 2) The proto2.Empty has minimum dependencies (no message_set or net/rpc dependencies) END GOOGLE-INTERNAL
+ { # An empty message that you can re-use to avoid defining duplicated empty
+ # messages in your project. A typical example is to use it as argument or the
+ # return value of a service API. For instance:
+ #
+ # service Foo {
+ # rpc Bar (proto2.Empty) returns (proto2.Empty) { };
+ # };
+ #
+ # BEGIN GOOGLE-INTERNAL
+ # The difference between this one and net/rpc/empty-message.proto is that
+ # 1) The generated message here is in proto2 C++ API.
+ # 2) The proto2.Empty has minimum dependencies
+ # (no message_set or net/rpc dependencies)
+ # END GOOGLE-INTERNAL
}</pre>
</div>
<div class="method">
<code class="details" id="publishBatch">publishBatch(body, x__xgafv=None)</code>
- <pre>Adds one or more messages to the topic. Returns NOT_FOUND if the topic does not exist.
+ <pre>Adds one or more messages to the topic. Returns NOT_FOUND if the topic does
+not exist.
Args:
body: object, The request body. (required)
@@ -231,27 +303,54 @@
"topic": "A String", # The messages in the request will be published on this topic.
"messages": [ # The messages to publish.
{ # A message data and its labels.
- "messageId": "A String", # 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.
- "data": "A String", # The message payload.
- "publishTime": "A String", # The time at which the message was published. The time is milliseconds since the UNIX epoch.
- "label": [ # Optional list of labels for this message. Keys in this collection must be unique.
+ "label": [ # Optional list of labels for this message. Keys in this collection must
+ # be unique.
{ # A key-value pair applied to a given object.
"numValue": "A String", # An integer value.
"strValue": "A String", # A string value.
- "key": "A String", # The key of a label is a syntactically valid URL (as per RFC 1738) with the "scheme" and initial slashes omitted and with the additional restrictions noted below. Each key should be globally unique. The "host" portion is called the "namespace" 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 "/" kpath kpath = ksegment *[ "/" ksegment ] ksegment = alphadigit | *[ alphadigit | "-" | "_" | "." ] where "hostname" and "alphadigit" are defined as in RFC 1738. Example key: spanner.google.com/universe
+ "key": "A String", # The key of a label is a syntactically valid URL (as per RFC 1738) with
+ # the "scheme" and initial slashes omitted and with the additional
+ # restrictions noted below. Each key should be globally unique. The
+ # "host" portion is called the "namespace" 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 "/" kpath
+ # kpath = ksegment *[ "/" ksegment ]
+ # ksegment = alphadigit | *[ alphadigit | "-" | "_" | "." ]
+ #
+ # where "hostname" and "alphadigit" are defined as in RFC 1738.
+ #
+ # Example key:
+ # spanner.google.com/universe
},
],
+ "data": "A String", # The message payload.
+ "publishTime": "A String", # The time at which the message was published.
+ # The time is milliseconds since the UNIX epoch.
+ "messageId": "A String", # 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.
},
],
}
x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
Returns:
An object of the form:
{ # Response for the PublishBatch method.
- "messageIds": [ # The server-assigned ID of each published message, in the same order as the messages in the request. IDs are guaranteed to be unique within the topic.
+ "messageIds": [ # The server-assigned ID of each published message, in the same order as
+ # the messages in the request. IDs are guaranteed to be unique within
+ # the topic.
"A String",
],
}</pre>