Class Subscription (1.5.0)

Stay organized with collections Save and categorize content based on your preferences.

A subscription resource. .. attribute:: name

Required. The name of the subscription. It must have the format "projects/{project}/subscriptions/{subscription}". {subscription} must start with a letter, and contain only letters ([A-Za-z]), numbers ([0-9]), dashes (-), underscores (_), periods (.), tildes (````), plus (+) or percent signs (%). It must be between 3 and 255 characters in length, and it must not start with"goog"``.

If push delivery is used with this subscription, this field is used to configure it. An empty pushConfig signifies that the subscriber will pull and ack messages using API methods.

Indicates whether to retain acknowledged messages. If true, then messages are not expunged from the subscription's backlog, even if they are acknowledged, until they fall out of the message_retention_duration window. This must be true if you would like to Seek to a timestamp.

See Creating and managing labels.

A policy that specifies the conditions for this subscription's expiration. A subscription is considered active as long as any connected subscriber is successfully consuming messages from the subscription or is issuing operations on the subscription. If expiration_policy is not set, a default policy with ttl of 31 days will be used. The minimum allowed value for expiration_policy.ttl is 1 day.

A policy that specifies the conditions for dead lettering messages in this subscription. If dead_letter_policy is not set, dead lettering is disabled. The Cloud Pub/Sub service account associated with this subscriptions's parent project (i.e., service-{project_number}@gcp-sa- must have permission to Acknowledge() messages on this subscription.


builtins.object > google.protobuf.pyext._message.CMessage > builtins.object > google.protobuf.message.Message > Subscription



API documentation for pubsub_v1.types.Subscription.LabelsEntry class.