OMGeeky/google-apis-rs
1
0
Fork 0
mirror of https://github.com/OMGeeky/google-apis-rs.git synced 2026-02-23 15:49:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

chore(json-update): update json and regen all code

Browse Source
This commit is contained in:
Sebastian Thiel
2015-06-26 16:08:25 +02:00
parent 615ac64ec1
commit 7d58d66025
596 changed files with 35453 additions and 5854 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
etc/api/pubsub/v1beta1/pubsub-api.json
View File

@@ -1,11 +1,11 @@
{
"kind": "discovery#restDescription",
"etag": "\"ye6orv2F-1npMW3u9suM3a7C5Bo/ZlS39JHAlE8Q0nTYVAdz5dw63po\"",
"etag": "\"ye6orv2F-1npMW3u9suM3a7C5Bo/GpjpDLvjZHTVKwwIavBHfgQL16c\"",
"discoveryVersion": "v1",
"id": "pubsub:v1beta1",
"name": "pubsub",
"version": "v1beta1",
"revision": "20150223",
"revision": "20150326",
"title": "Google Cloud Pub/Sub API",
"description": "Provides reliable, many-to-many, asynchronous messaging between applications.",
"ownerDomain": "google.com",
@@ -168,11 +168,18 @@
},
"ackId": {
"type": "string",
"description": "The acknowledgment ID."
"description": "The acknowledgment ID. Either this or ack_ids must be populated, not both."
},
"ackIds": {
"type": "array",
"description": "List of acknowledgment IDs. Either this field or ack_id should be populated, not both. TODO(handrei): mark the above field deprecated once it's not used internally.",
"items": {
"type": "string"
}
},
"subscription": {
"type": "string",
"description": "The name of the subscription from which messages are being pulled."
"description": "Next Index: 5 The name of the subscription from which messages are being pulled."
}
}
},
@@ -366,7 +373,7 @@
"properties": {
"ackDeadlineSeconds": {
"type": "integer",
"description": "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.\n\nFor push delivery, this value is used to set the request timeout for the call to the push endpoint.\n\nFor pull delivery, this value is used as the initial value for the Ack deadline. It may be overridden for a specific pull request (message) 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).",
"description": "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.\n\nFor push delivery, this value is used to set the request timeout for the call to the push endpoint.\n\nFor 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).",
"format": "int32"
},
"name": {