Update pubsub to v1beta2

The following is a checklist for migrating over to the new v1beta2 pubsub API. It lists the incompatible changes that occurred between the two APIs.

All requests now using a new url scheme: https://pubsub.googleapis.com/v1beta2/...

Subscriptions:

Topics:

NEW:

topics.subscriptions.list which results the name of the subscriptions for a particular topic.
PubSubMessage description which describes the pubsub message response for various requests.

Great list! Few additions.

labels renamed to attributes
resource name format changed; /topics/{projectid}/{topicname} to projects/{projectid}/topics/{topicname} and /subscriptions/{projectid}/{subscriptionname} to projects/{projectid}/subscriptions/{subscriptionname}

@tmatsuo

@tmatsuo So maxResults changed to pageSize, which is documented as "Maximum number of topics to return." Is this the max number of results returned PER PAGE i.e. if I have more results, then it will still give me a page token, or does it mean that it will only show me that many ever? Did this functionality change from the previous API or is it just better (or worsely) documented now?

Is this the max number of results returned PER PAGE
yes, the name of the parameter strongly suggests that.

if I have more results, then it will still give me a page token
yes.

Do you have any suggestions to improve things?

@tmatsuo

@tmatsuo I have some feedback. topics/subscriptions/list returns a list of subscription names where as subscriptions/list returns a list of Subscription objects. It would be nice if they both returned Subscription objects if possible.

Yes, good eye catching that discrepancy. I think however, this is because topics.subscriptions.list may return subscriptions in other project, and thus the API issuer may not have permission to access them.

It doesn't make sense that it will show me subscriptions for other projects because we specify a specific project on request. Also why would it show me the names of subscriptions if I don't have access to use them in the first place? This would seem like a violation of permissions. I don't want someone seeing my subscriptions on my project if they don't have access to it.

It doesn't make sense that it will show me subscriptions for other projects because we specify a specific project on request.

Not true. With the bare API, you can create a subscription in project1 attached to a topic in project2.

This would seem like a violation of permissions. I don't want someone seeing my subscriptions on my project if they don't have access to it.

When creating that subscription, the creator said explicitly "I subscribe to this topic". So I think seeing only the subscription name with the topic read permission seems OK to me.

You can't get the internal data of that subscription if you don't have a permission.