Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
google-native.pubsub/v1.getSubscription
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
Gets the configuration details of a subscription.
Using getSubscription
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getSubscription(args: GetSubscriptionArgs, opts?: InvokeOptions): Promise<GetSubscriptionResult>
function getSubscriptionOutput(args: GetSubscriptionOutputArgs, opts?: InvokeOptions): Output<GetSubscriptionResult>
def get_subscription(project: Optional[str] = None,
subscription_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetSubscriptionResult
def get_subscription_output(project: Optional[pulumi.Input[str]] = None,
subscription_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetSubscriptionResult]
func LookupSubscription(ctx *Context, args *LookupSubscriptionArgs, opts ...InvokeOption) (*LookupSubscriptionResult, error)
func LookupSubscriptionOutput(ctx *Context, args *LookupSubscriptionOutputArgs, opts ...InvokeOption) LookupSubscriptionResultOutput
> Note: This function is named LookupSubscription
in the Go SDK.
public static class GetSubscription
{
public static Task<GetSubscriptionResult> InvokeAsync(GetSubscriptionArgs args, InvokeOptions? opts = null)
public static Output<GetSubscriptionResult> Invoke(GetSubscriptionInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetSubscriptionResult> getSubscription(GetSubscriptionArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:pubsub/v1:getSubscription
arguments:
# arguments dictionary
The following arguments are supported:
- Subscription
Id string - Project string
- Subscription
Id string - Project string
- subscription
Id String - project String
- subscription
Id string - project string
- subscription_
id str - project str
- subscription
Id String - project String
getSubscription Result
The following output properties are available:
- Ack
Deadline intSeconds - Optional. The approximate amount of time (on a best-effort basis) Pub/Sub waits for the subscriber to acknowledge receipt before resending the message. In the interval after the message is delivered and before it is acknowledged, it is considered to be outstanding. During that time period, the message will not be redelivered (on a best-effort basis). For pull subscriptions, this value is used as the initial value for the ack deadline. To override this value for a given message, call
ModifyAckDeadline
with the correspondingack_id
if using non-streaming pull or send theack_id
in aStreamingModifyAckDeadlineRequest
if using streaming pull. The minimum custom deadline you can specify is 10 seconds. The maximum custom deadline you can specify is 600 seconds (10 minutes). If this parameter is 0, a default value of 10 seconds is used. For push delivery, this value is also used to set the request timeout for the call to the push endpoint. If the subscriber never acknowledges the message, the Pub/Sub system will eventually redeliver the message. - Bigquery
Config Pulumi.Google Native. Pubsub. V1. Outputs. Big Query Config Response - Optional. If delivery to BigQuery is used with this subscription, this field is used to configure it.
- Cloud
Storage Pulumi.Config Google Native. Pubsub. V1. Outputs. Cloud Storage Config Response - Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
- Dead
Letter Pulumi.Policy Google Native. Pubsub. V1. Outputs. Dead Letter Policy Response - Optional. 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 Pub/Sub service account associated with this subscriptions's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Acknowledge() messages on this subscription.
- Detached bool
- Optional. Indicates whether the subscription is detached from its topic. Detached subscriptions don't receive messages from their topic and don't retain any backlog.
Pull
andStreamingPull
requests will return FAILED_PRECONDITION. If the subscription is a push subscription, pushes to the endpoint will not be made. - Enable
Exactly boolOnce Delivery - Optional. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of
message_id
on this subscription: * The message sent to a subscriber is guaranteed not to be resent before the message's acknowledgement deadline expires. * An acknowledged message will not be resent to a subscriber. Note that subscribers may still receive multiple copies of a message whenenable_exactly_once_delivery
is true if the message was published multiple times by a publisher client. These copies are considered distinct by Pub/Sub and have distinctmessage_id
values. - Enable
Message boolOrdering - Optional. If true, messages published with the same
ordering_key
inPubsubMessage
will be delivered to the subscribers in the order in which they are received by the Pub/Sub system. Otherwise, they may be delivered in any order. - Expiration
Policy Pulumi.Google Native. Pubsub. V1. Outputs. Expiration Policy Response - Optional. 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 withttl
of 31 days will be used. The minimum allowed value forexpiration_policy.ttl
is 1 day. Ifexpiration_policy
is set, butexpiration_policy.ttl
is not set, the subscription never expires. - Filter string
- Optional. An expression written in the Pub/Sub filter language. If non-empty, then only
PubsubMessage
s whoseattributes
field matches the filter are delivered on this subscription. If empty, then no messages are filtered out. - Labels Dictionary<string, string>
- Optional. See Creating and managing labels.
- Message
Retention stringDuration - Optional. How long to retain unacknowledged messages in the subscription's backlog, from the moment a message is published. If
retain_acked_messages
is true, then this also configures the retention of acknowledged messages, and thus configures how far back in time aSeek
can be done. Defaults to 7 days. Cannot be more than 7 days or less than 10 minutes. - Name string
- 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"
. - Push
Config Pulumi.Google Native. Pubsub. V1. Outputs. Push Config Response - Optional. If push delivery is used with this subscription, this field is used to configure it.
- Retain
Acked boolMessages - Optional. 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] (https://cloud.google.com/pubsub/docs/replay-overview#seek_to_a_time) in the past to replay previously-acknowledged messages. - Retry
Policy Pulumi.Google Native. Pubsub. V1. Outputs. Retry Policy Response - Optional. A policy that specifies how Pub/Sub retries message delivery for this subscription. If not set, the default retry policy is applied. This generally implies that messages will be retried as soon as possible for healthy subscribers. RetryPolicy will be triggered on NACKs or acknowledgement deadline exceeded events for a given message.
- State string
- An output-only field indicating whether or not the subscription can receive messages.
- Topic string
- The name of the topic from which this subscription is receiving messages. Format is
projects/{project}/topics/{topic}
. The value of this field will be_deleted-topic_
if the topic has been deleted. - Topic
Message stringRetention Duration - Indicates the minimum duration for which a message is retained after it is published to the subscription's topic. If this field is set, messages published to the subscription's topic in the last
topic_message_retention_duration
are always available to subscribers. See themessage_retention_duration
field inTopic
. This field is set only in responses from the server; it is ignored if it is set in any requests.
- Ack
Deadline intSeconds - Optional. The approximate amount of time (on a best-effort basis) Pub/Sub waits for the subscriber to acknowledge receipt before resending the message. In the interval after the message is delivered and before it is acknowledged, it is considered to be outstanding. During that time period, the message will not be redelivered (on a best-effort basis). For pull subscriptions, this value is used as the initial value for the ack deadline. To override this value for a given message, call
ModifyAckDeadline
with the correspondingack_id
if using non-streaming pull or send theack_id
in aStreamingModifyAckDeadlineRequest
if using streaming pull. The minimum custom deadline you can specify is 10 seconds. The maximum custom deadline you can specify is 600 seconds (10 minutes). If this parameter is 0, a default value of 10 seconds is used. For push delivery, this value is also used to set the request timeout for the call to the push endpoint. If the subscriber never acknowledges the message, the Pub/Sub system will eventually redeliver the message. - Bigquery
Config BigQuery Config Response - Optional. If delivery to BigQuery is used with this subscription, this field is used to configure it.
- Cloud
Storage CloudConfig Storage Config Response - Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
- Dead
Letter DeadPolicy Letter Policy Response - Optional. 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 Pub/Sub service account associated with this subscriptions's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Acknowledge() messages on this subscription.
- Detached bool
- Optional. Indicates whether the subscription is detached from its topic. Detached subscriptions don't receive messages from their topic and don't retain any backlog.
Pull
andStreamingPull
requests will return FAILED_PRECONDITION. If the subscription is a push subscription, pushes to the endpoint will not be made. - Enable
Exactly boolOnce Delivery - Optional. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of
message_id
on this subscription: * The message sent to a subscriber is guaranteed not to be resent before the message's acknowledgement deadline expires. * An acknowledged message will not be resent to a subscriber. Note that subscribers may still receive multiple copies of a message whenenable_exactly_once_delivery
is true if the message was published multiple times by a publisher client. These copies are considered distinct by Pub/Sub and have distinctmessage_id
values. - Enable
Message boolOrdering - Optional. If true, messages published with the same
ordering_key
inPubsubMessage
will be delivered to the subscribers in the order in which they are received by the Pub/Sub system. Otherwise, they may be delivered in any order. - Expiration
Policy ExpirationPolicy Response - Optional. 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 withttl
of 31 days will be used. The minimum allowed value forexpiration_policy.ttl
is 1 day. Ifexpiration_policy
is set, butexpiration_policy.ttl
is not set, the subscription never expires. - Filter string
- Optional. An expression written in the Pub/Sub filter language. If non-empty, then only
PubsubMessage
s whoseattributes
field matches the filter are delivered on this subscription. If empty, then no messages are filtered out. - Labels map[string]string
- Optional. See Creating and managing labels.
- Message
Retention stringDuration - Optional. How long to retain unacknowledged messages in the subscription's backlog, from the moment a message is published. If
retain_acked_messages
is true, then this also configures the retention of acknowledged messages, and thus configures how far back in time aSeek
can be done. Defaults to 7 days. Cannot be more than 7 days or less than 10 minutes. - Name string
- 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"
. - Push
Config PushConfig Response - Optional. If push delivery is used with this subscription, this field is used to configure it.
- Retain
Acked boolMessages - Optional. 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] (https://cloud.google.com/pubsub/docs/replay-overview#seek_to_a_time) in the past to replay previously-acknowledged messages. - Retry
Policy RetryPolicy Response - Optional. A policy that specifies how Pub/Sub retries message delivery for this subscription. If not set, the default retry policy is applied. This generally implies that messages will be retried as soon as possible for healthy subscribers. RetryPolicy will be triggered on NACKs or acknowledgement deadline exceeded events for a given message.
- State string
- An output-only field indicating whether or not the subscription can receive messages.
- Topic string
- The name of the topic from which this subscription is receiving messages. Format is
projects/{project}/topics/{topic}
. The value of this field will be_deleted-topic_
if the topic has been deleted. - Topic
Message stringRetention Duration - Indicates the minimum duration for which a message is retained after it is published to the subscription's topic. If this field is set, messages published to the subscription's topic in the last
topic_message_retention_duration
are always available to subscribers. See themessage_retention_duration
field inTopic
. This field is set only in responses from the server; it is ignored if it is set in any requests.
- ack
Deadline IntegerSeconds - Optional. The approximate amount of time (on a best-effort basis) Pub/Sub waits for the subscriber to acknowledge receipt before resending the message. In the interval after the message is delivered and before it is acknowledged, it is considered to be outstanding. During that time period, the message will not be redelivered (on a best-effort basis). For pull subscriptions, this value is used as the initial value for the ack deadline. To override this value for a given message, call
ModifyAckDeadline
with the correspondingack_id
if using non-streaming pull or send theack_id
in aStreamingModifyAckDeadlineRequest
if using streaming pull. The minimum custom deadline you can specify is 10 seconds. The maximum custom deadline you can specify is 600 seconds (10 minutes). If this parameter is 0, a default value of 10 seconds is used. For push delivery, this value is also used to set the request timeout for the call to the push endpoint. If the subscriber never acknowledges the message, the Pub/Sub system will eventually redeliver the message. - bigquery
Config BigQuery Config Response - Optional. If delivery to BigQuery is used with this subscription, this field is used to configure it.
- cloud
Storage CloudConfig Storage Config Response - Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
- dead
Letter DeadPolicy Letter Policy Response - Optional. 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 Pub/Sub service account associated with this subscriptions's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Acknowledge() messages on this subscription.
- detached Boolean
- Optional. Indicates whether the subscription is detached from its topic. Detached subscriptions don't receive messages from their topic and don't retain any backlog.
Pull
andStreamingPull
requests will return FAILED_PRECONDITION. If the subscription is a push subscription, pushes to the endpoint will not be made. - enable
Exactly BooleanOnce Delivery - Optional. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of
message_id
on this subscription: * The message sent to a subscriber is guaranteed not to be resent before the message's acknowledgement deadline expires. * An acknowledged message will not be resent to a subscriber. Note that subscribers may still receive multiple copies of a message whenenable_exactly_once_delivery
is true if the message was published multiple times by a publisher client. These copies are considered distinct by Pub/Sub and have distinctmessage_id
values. - enable
Message BooleanOrdering - Optional. If true, messages published with the same
ordering_key
inPubsubMessage
will be delivered to the subscribers in the order in which they are received by the Pub/Sub system. Otherwise, they may be delivered in any order. - expiration
Policy ExpirationPolicy Response - Optional. 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 withttl
of 31 days will be used. The minimum allowed value forexpiration_policy.ttl
is 1 day. Ifexpiration_policy
is set, butexpiration_policy.ttl
is not set, the subscription never expires. - filter String
- Optional. An expression written in the Pub/Sub filter language. If non-empty, then only
PubsubMessage
s whoseattributes
field matches the filter are delivered on this subscription. If empty, then no messages are filtered out. - labels Map<String,String>
- Optional. See Creating and managing labels.
- message
Retention StringDuration - Optional. How long to retain unacknowledged messages in the subscription's backlog, from the moment a message is published. If
retain_acked_messages
is true, then this also configures the retention of acknowledged messages, and thus configures how far back in time aSeek
can be done. Defaults to 7 days. Cannot be more than 7 days or less than 10 minutes. - name String
- 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"
. - push
Config PushConfig Response - Optional. If push delivery is used with this subscription, this field is used to configure it.
- retain
Acked BooleanMessages - Optional. 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] (https://cloud.google.com/pubsub/docs/replay-overview#seek_to_a_time) in the past to replay previously-acknowledged messages. - retry
Policy RetryPolicy Response - Optional. A policy that specifies how Pub/Sub retries message delivery for this subscription. If not set, the default retry policy is applied. This generally implies that messages will be retried as soon as possible for healthy subscribers. RetryPolicy will be triggered on NACKs or acknowledgement deadline exceeded events for a given message.
- state String
- An output-only field indicating whether or not the subscription can receive messages.
- topic String
- The name of the topic from which this subscription is receiving messages. Format is
projects/{project}/topics/{topic}
. The value of this field will be_deleted-topic_
if the topic has been deleted. - topic
Message StringRetention Duration - Indicates the minimum duration for which a message is retained after it is published to the subscription's topic. If this field is set, messages published to the subscription's topic in the last
topic_message_retention_duration
are always available to subscribers. See themessage_retention_duration
field inTopic
. This field is set only in responses from the server; it is ignored if it is set in any requests.
- ack
Deadline numberSeconds - Optional. The approximate amount of time (on a best-effort basis) Pub/Sub waits for the subscriber to acknowledge receipt before resending the message. In the interval after the message is delivered and before it is acknowledged, it is considered to be outstanding. During that time period, the message will not be redelivered (on a best-effort basis). For pull subscriptions, this value is used as the initial value for the ack deadline. To override this value for a given message, call
ModifyAckDeadline
with the correspondingack_id
if using non-streaming pull or send theack_id
in aStreamingModifyAckDeadlineRequest
if using streaming pull. The minimum custom deadline you can specify is 10 seconds. The maximum custom deadline you can specify is 600 seconds (10 minutes). If this parameter is 0, a default value of 10 seconds is used. For push delivery, this value is also used to set the request timeout for the call to the push endpoint. If the subscriber never acknowledges the message, the Pub/Sub system will eventually redeliver the message. - bigquery
Config BigQuery Config Response - Optional. If delivery to BigQuery is used with this subscription, this field is used to configure it.
- cloud
Storage CloudConfig Storage Config Response - Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
- dead
Letter DeadPolicy Letter Policy Response - Optional. 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 Pub/Sub service account associated with this subscriptions's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Acknowledge() messages on this subscription.
- detached boolean
- Optional. Indicates whether the subscription is detached from its topic. Detached subscriptions don't receive messages from their topic and don't retain any backlog.
Pull
andStreamingPull
requests will return FAILED_PRECONDITION. If the subscription is a push subscription, pushes to the endpoint will not be made. - enable
Exactly booleanOnce Delivery - Optional. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of
message_id
on this subscription: * The message sent to a subscriber is guaranteed not to be resent before the message's acknowledgement deadline expires. * An acknowledged message will not be resent to a subscriber. Note that subscribers may still receive multiple copies of a message whenenable_exactly_once_delivery
is true if the message was published multiple times by a publisher client. These copies are considered distinct by Pub/Sub and have distinctmessage_id
values. - enable
Message booleanOrdering - Optional. If true, messages published with the same
ordering_key
inPubsubMessage
will be delivered to the subscribers in the order in which they are received by the Pub/Sub system. Otherwise, they may be delivered in any order. - expiration
Policy ExpirationPolicy Response - Optional. 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 withttl
of 31 days will be used. The minimum allowed value forexpiration_policy.ttl
is 1 day. Ifexpiration_policy
is set, butexpiration_policy.ttl
is not set, the subscription never expires. - filter string
- Optional. An expression written in the Pub/Sub filter language. If non-empty, then only
PubsubMessage
s whoseattributes
field matches the filter are delivered on this subscription. If empty, then no messages are filtered out. - labels {[key: string]: string}
- Optional. See Creating and managing labels.
- message
Retention stringDuration - Optional. How long to retain unacknowledged messages in the subscription's backlog, from the moment a message is published. If
retain_acked_messages
is true, then this also configures the retention of acknowledged messages, and thus configures how far back in time aSeek
can be done. Defaults to 7 days. Cannot be more than 7 days or less than 10 minutes. - name string
- 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"
. - push
Config PushConfig Response - Optional. If push delivery is used with this subscription, this field is used to configure it.
- retain
Acked booleanMessages - Optional. 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] (https://cloud.google.com/pubsub/docs/replay-overview#seek_to_a_time) in the past to replay previously-acknowledged messages. - retry
Policy RetryPolicy Response - Optional. A policy that specifies how Pub/Sub retries message delivery for this subscription. If not set, the default retry policy is applied. This generally implies that messages will be retried as soon as possible for healthy subscribers. RetryPolicy will be triggered on NACKs or acknowledgement deadline exceeded events for a given message.
- state string
- An output-only field indicating whether or not the subscription can receive messages.
- topic string
- The name of the topic from which this subscription is receiving messages. Format is
projects/{project}/topics/{topic}
. The value of this field will be_deleted-topic_
if the topic has been deleted. - topic
Message stringRetention Duration - Indicates the minimum duration for which a message is retained after it is published to the subscription's topic. If this field is set, messages published to the subscription's topic in the last
topic_message_retention_duration
are always available to subscribers. See themessage_retention_duration
field inTopic
. This field is set only in responses from the server; it is ignored if it is set in any requests.
- ack_
deadline_ intseconds - Optional. The approximate amount of time (on a best-effort basis) Pub/Sub waits for the subscriber to acknowledge receipt before resending the message. In the interval after the message is delivered and before it is acknowledged, it is considered to be outstanding. During that time period, the message will not be redelivered (on a best-effort basis). For pull subscriptions, this value is used as the initial value for the ack deadline. To override this value for a given message, call
ModifyAckDeadline
with the correspondingack_id
if using non-streaming pull or send theack_id
in aStreamingModifyAckDeadlineRequest
if using streaming pull. The minimum custom deadline you can specify is 10 seconds. The maximum custom deadline you can specify is 600 seconds (10 minutes). If this parameter is 0, a default value of 10 seconds is used. For push delivery, this value is also used to set the request timeout for the call to the push endpoint. If the subscriber never acknowledges the message, the Pub/Sub system will eventually redeliver the message. - bigquery_
config BigQuery Config Response - Optional. If delivery to BigQuery is used with this subscription, this field is used to configure it.
- cloud_
storage_ Cloudconfig Storage Config Response - Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
- dead_
letter_ Deadpolicy Letter Policy Response - Optional. 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 Pub/Sub service account associated with this subscriptions's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Acknowledge() messages on this subscription.
- detached bool
- Optional. Indicates whether the subscription is detached from its topic. Detached subscriptions don't receive messages from their topic and don't retain any backlog.
Pull
andStreamingPull
requests will return FAILED_PRECONDITION. If the subscription is a push subscription, pushes to the endpoint will not be made. - enable_
exactly_ boolonce_ delivery - Optional. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of
message_id
on this subscription: * The message sent to a subscriber is guaranteed not to be resent before the message's acknowledgement deadline expires. * An acknowledged message will not be resent to a subscriber. Note that subscribers may still receive multiple copies of a message whenenable_exactly_once_delivery
is true if the message was published multiple times by a publisher client. These copies are considered distinct by Pub/Sub and have distinctmessage_id
values. - enable_
message_ boolordering - Optional. If true, messages published with the same
ordering_key
inPubsubMessage
will be delivered to the subscribers in the order in which they are received by the Pub/Sub system. Otherwise, they may be delivered in any order. - expiration_
policy ExpirationPolicy Response - Optional. 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 withttl
of 31 days will be used. The minimum allowed value forexpiration_policy.ttl
is 1 day. Ifexpiration_policy
is set, butexpiration_policy.ttl
is not set, the subscription never expires. - filter str
- Optional. An expression written in the Pub/Sub filter language. If non-empty, then only
PubsubMessage
s whoseattributes
field matches the filter are delivered on this subscription. If empty, then no messages are filtered out. - labels Mapping[str, str]
- Optional. See Creating and managing labels.
- message_
retention_ strduration - Optional. How long to retain unacknowledged messages in the subscription's backlog, from the moment a message is published. If
retain_acked_messages
is true, then this also configures the retention of acknowledged messages, and thus configures how far back in time aSeek
can be done. Defaults to 7 days. Cannot be more than 7 days or less than 10 minutes. - name str
- 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"
. - push_
config PushConfig Response - Optional. If push delivery is used with this subscription, this field is used to configure it.
- retain_
acked_ boolmessages - Optional. 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] (https://cloud.google.com/pubsub/docs/replay-overview#seek_to_a_time) in the past to replay previously-acknowledged messages. - retry_
policy RetryPolicy Response - Optional. A policy that specifies how Pub/Sub retries message delivery for this subscription. If not set, the default retry policy is applied. This generally implies that messages will be retried as soon as possible for healthy subscribers. RetryPolicy will be triggered on NACKs or acknowledgement deadline exceeded events for a given message.
- state str
- An output-only field indicating whether or not the subscription can receive messages.
- topic str
- The name of the topic from which this subscription is receiving messages. Format is
projects/{project}/topics/{topic}
. The value of this field will be_deleted-topic_
if the topic has been deleted. - topic_
message_ strretention_ duration - Indicates the minimum duration for which a message is retained after it is published to the subscription's topic. If this field is set, messages published to the subscription's topic in the last
topic_message_retention_duration
are always available to subscribers. See themessage_retention_duration
field inTopic
. This field is set only in responses from the server; it is ignored if it is set in any requests.
- ack
Deadline NumberSeconds - Optional. The approximate amount of time (on a best-effort basis) Pub/Sub waits for the subscriber to acknowledge receipt before resending the message. In the interval after the message is delivered and before it is acknowledged, it is considered to be outstanding. During that time period, the message will not be redelivered (on a best-effort basis). For pull subscriptions, this value is used as the initial value for the ack deadline. To override this value for a given message, call
ModifyAckDeadline
with the correspondingack_id
if using non-streaming pull or send theack_id
in aStreamingModifyAckDeadlineRequest
if using streaming pull. The minimum custom deadline you can specify is 10 seconds. The maximum custom deadline you can specify is 600 seconds (10 minutes). If this parameter is 0, a default value of 10 seconds is used. For push delivery, this value is also used to set the request timeout for the call to the push endpoint. If the subscriber never acknowledges the message, the Pub/Sub system will eventually redeliver the message. - bigquery
Config Property Map - Optional. If delivery to BigQuery is used with this subscription, this field is used to configure it.
- cloud
Storage Property MapConfig - Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
- dead
Letter Property MapPolicy - Optional. 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 Pub/Sub service account associated with this subscriptions's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Acknowledge() messages on this subscription.
- detached Boolean
- Optional. Indicates whether the subscription is detached from its topic. Detached subscriptions don't receive messages from their topic and don't retain any backlog.
Pull
andStreamingPull
requests will return FAILED_PRECONDITION. If the subscription is a push subscription, pushes to the endpoint will not be made. - enable
Exactly BooleanOnce Delivery - Optional. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of
message_id
on this subscription: * The message sent to a subscriber is guaranteed not to be resent before the message's acknowledgement deadline expires. * An acknowledged message will not be resent to a subscriber. Note that subscribers may still receive multiple copies of a message whenenable_exactly_once_delivery
is true if the message was published multiple times by a publisher client. These copies are considered distinct by Pub/Sub and have distinctmessage_id
values. - enable
Message BooleanOrdering - Optional. If true, messages published with the same
ordering_key
inPubsubMessage
will be delivered to the subscribers in the order in which they are received by the Pub/Sub system. Otherwise, they may be delivered in any order. - expiration
Policy Property Map - Optional. 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 withttl
of 31 days will be used. The minimum allowed value forexpiration_policy.ttl
is 1 day. Ifexpiration_policy
is set, butexpiration_policy.ttl
is not set, the subscription never expires. - filter String
- Optional. An expression written in the Pub/Sub filter language. If non-empty, then only
PubsubMessage
s whoseattributes
field matches the filter are delivered on this subscription. If empty, then no messages are filtered out. - labels Map<String>
- Optional. See Creating and managing labels.
- message
Retention StringDuration - Optional. How long to retain unacknowledged messages in the subscription's backlog, from the moment a message is published. If
retain_acked_messages
is true, then this also configures the retention of acknowledged messages, and thus configures how far back in time aSeek
can be done. Defaults to 7 days. Cannot be more than 7 days or less than 10 minutes. - name String
- 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"
. - push
Config Property Map - Optional. If push delivery is used with this subscription, this field is used to configure it.
- retain
Acked BooleanMessages - Optional. 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] (https://cloud.google.com/pubsub/docs/replay-overview#seek_to_a_time) in the past to replay previously-acknowledged messages. - retry
Policy Property Map - Optional. A policy that specifies how Pub/Sub retries message delivery for this subscription. If not set, the default retry policy is applied. This generally implies that messages will be retried as soon as possible for healthy subscribers. RetryPolicy will be triggered on NACKs or acknowledgement deadline exceeded events for a given message.
- state String
- An output-only field indicating whether or not the subscription can receive messages.
- topic String
- The name of the topic from which this subscription is receiving messages. Format is
projects/{project}/topics/{topic}
. The value of this field will be_deleted-topic_
if the topic has been deleted. - topic
Message StringRetention Duration - Indicates the minimum duration for which a message is retained after it is published to the subscription's topic. If this field is set, messages published to the subscription's topic in the last
topic_message_retention_duration
are always available to subscribers. See themessage_retention_duration
field inTopic
. This field is set only in responses from the server; it is ignored if it is set in any requests.
Supporting Types
AvroConfigResponse
- Write
Metadata bool - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.
- Write
Metadata bool - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.
- write
Metadata Boolean - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.
- write
Metadata boolean - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.
- write_
metadata bool - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.
- write
Metadata Boolean - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key as additional fields in the output. The subscription name, message_id, and publish_time fields are put in their own fields while all other message properties other than data (for example, an ordering_key, if present) are added as entries in the attributes map.
BigQueryConfigResponse
- Drop
Unknown boolFields - Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription's backlog.
- State string
- An output-only field that indicates whether or not the subscription can receive messages.
- Table string
- Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
- Use
Topic boolSchema - Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists.
- Write
Metadata bool - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
- Drop
Unknown boolFields - Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription's backlog.
- State string
- An output-only field that indicates whether or not the subscription can receive messages.
- Table string
- Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
- Use
Topic boolSchema - Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists.
- Write
Metadata bool - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
- drop
Unknown BooleanFields - Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription's backlog.
- state String
- An output-only field that indicates whether or not the subscription can receive messages.
- table String
- Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
- use
Topic BooleanSchema - Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists.
- write
Metadata Boolean - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
- drop
Unknown booleanFields - Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription's backlog.
- state string
- An output-only field that indicates whether or not the subscription can receive messages.
- table string
- Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
- use
Topic booleanSchema - Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists.
- write
Metadata boolean - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
- drop_
unknown_ boolfields - Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription's backlog.
- state str
- An output-only field that indicates whether or not the subscription can receive messages.
- table str
- Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
- use_
topic_ boolschema - Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists.
- write_
metadata bool - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
- drop
Unknown BooleanFields - Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription's backlog.
- state String
- An output-only field that indicates whether or not the subscription can receive messages.
- table String
- Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
- use
Topic BooleanSchema - Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists.
- write
Metadata Boolean - Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
CloudStorageConfigResponse
- Avro
Config Pulumi.Google Native. Pubsub. V1. Inputs. Avro Config Response - Optional. If set, message data will be written to Cloud Storage in Avro format.
- Bucket string
- User-provided name for the Cloud Storage bucket. The bucket must be created by the user. The bucket name must be without any prefix like "gs://". See the [bucket naming requirements] (https://cloud.google.com/storage/docs/buckets#naming).
- Filename
Prefix string - Optional. User-provided prefix for Cloud Storage filename. See the object naming requirements.
- Filename
Suffix string - Optional. User-provided suffix for Cloud Storage filename. See the object naming requirements. Must not end in "/".
- Max
Bytes string - Optional. The maximum bytes that can be written to a Cloud Storage file before a new file is created. Min 1 KB, max 10 GiB. The max_bytes limit may be exceeded in cases where messages are larger than the limit.
- Max
Duration string - Optional. The maximum duration that can elapse before a new Cloud Storage file is created. Min 1 minute, max 10 minutes, default 5 minutes. May not exceed the subscription's acknowledgement deadline.
- State string
- An output-only field that indicates whether or not the subscription can receive messages.
- Text
Config Pulumi.Google Native. Pubsub. V1. Inputs. Text Config Response - Optional. If set, message data will be written to Cloud Storage in text format.
- Avro
Config AvroConfig Response - Optional. If set, message data will be written to Cloud Storage in Avro format.
- Bucket string
- User-provided name for the Cloud Storage bucket. The bucket must be created by the user. The bucket name must be without any prefix like "gs://". See the [bucket naming requirements] (https://cloud.google.com/storage/docs/buckets#naming).
- Filename
Prefix string - Optional. User-provided prefix for Cloud Storage filename. See the object naming requirements.
- Filename
Suffix string - Optional. User-provided suffix for Cloud Storage filename. See the object naming requirements. Must not end in "/".
- Max
Bytes string - Optional. The maximum bytes that can be written to a Cloud Storage file before a new file is created. Min 1 KB, max 10 GiB. The max_bytes limit may be exceeded in cases where messages are larger than the limit.
- Max
Duration string - Optional. The maximum duration that can elapse before a new Cloud Storage file is created. Min 1 minute, max 10 minutes, default 5 minutes. May not exceed the subscription's acknowledgement deadline.
- State string
- An output-only field that indicates whether or not the subscription can receive messages.
- Text
Config TextConfig Response - Optional. If set, message data will be written to Cloud Storage in text format.
- avro
Config AvroConfig Response - Optional. If set, message data will be written to Cloud Storage in Avro format.
- bucket String
- User-provided name for the Cloud Storage bucket. The bucket must be created by the user. The bucket name must be without any prefix like "gs://". See the [bucket naming requirements] (https://cloud.google.com/storage/docs/buckets#naming).
- filename
Prefix String - Optional. User-provided prefix for Cloud Storage filename. See the object naming requirements.
- filename
Suffix String - Optional. User-provided suffix for Cloud Storage filename. See the object naming requirements. Must not end in "/".
- max
Bytes String - Optional. The maximum bytes that can be written to a Cloud Storage file before a new file is created. Min 1 KB, max 10 GiB. The max_bytes limit may be exceeded in cases where messages are larger than the limit.
- max
Duration String - Optional. The maximum duration that can elapse before a new Cloud Storage file is created. Min 1 minute, max 10 minutes, default 5 minutes. May not exceed the subscription's acknowledgement deadline.
- state String
- An output-only field that indicates whether or not the subscription can receive messages.
- text
Config TextConfig Response - Optional. If set, message data will be written to Cloud Storage in text format.
- avro
Config AvroConfig Response - Optional. If set, message data will be written to Cloud Storage in Avro format.
- bucket string
- User-provided name for the Cloud Storage bucket. The bucket must be created by the user. The bucket name must be without any prefix like "gs://". See the [bucket naming requirements] (https://cloud.google.com/storage/docs/buckets#naming).
- filename
Prefix string - Optional. User-provided prefix for Cloud Storage filename. See the object naming requirements.
- filename
Suffix string - Optional. User-provided suffix for Cloud Storage filename. See the object naming requirements. Must not end in "/".
- max
Bytes string - Optional. The maximum bytes that can be written to a Cloud Storage file before a new file is created. Min 1 KB, max 10 GiB. The max_bytes limit may be exceeded in cases where messages are larger than the limit.
- max
Duration string - Optional. The maximum duration that can elapse before a new Cloud Storage file is created. Min 1 minute, max 10 minutes, default 5 minutes. May not exceed the subscription's acknowledgement deadline.
- state string
- An output-only field that indicates whether or not the subscription can receive messages.
- text
Config TextConfig Response - Optional. If set, message data will be written to Cloud Storage in text format.
- avro_
config AvroConfig Response - Optional. If set, message data will be written to Cloud Storage in Avro format.
- bucket str
- User-provided name for the Cloud Storage bucket. The bucket must be created by the user. The bucket name must be without any prefix like "gs://". See the [bucket naming requirements] (https://cloud.google.com/storage/docs/buckets#naming).
- filename_
prefix str - Optional. User-provided prefix for Cloud Storage filename. See the object naming requirements.
- filename_
suffix str - Optional. User-provided suffix for Cloud Storage filename. See the object naming requirements. Must not end in "/".
- max_
bytes str - Optional. The maximum bytes that can be written to a Cloud Storage file before a new file is created. Min 1 KB, max 10 GiB. The max_bytes limit may be exceeded in cases where messages are larger than the limit.
- max_
duration str - Optional. The maximum duration that can elapse before a new Cloud Storage file is created. Min 1 minute, max 10 minutes, default 5 minutes. May not exceed the subscription's acknowledgement deadline.
- state str
- An output-only field that indicates whether or not the subscription can receive messages.
- text_
config TextConfig Response - Optional. If set, message data will be written to Cloud Storage in text format.
- avro
Config Property Map - Optional. If set, message data will be written to Cloud Storage in Avro format.
- bucket String
- User-provided name for the Cloud Storage bucket. The bucket must be created by the user. The bucket name must be without any prefix like "gs://". See the [bucket naming requirements] (https://cloud.google.com/storage/docs/buckets#naming).
- filename
Prefix String - Optional. User-provided prefix for Cloud Storage filename. See the object naming requirements.
- filename
Suffix String - Optional. User-provided suffix for Cloud Storage filename. See the object naming requirements. Must not end in "/".
- max
Bytes String - Optional. The maximum bytes that can be written to a Cloud Storage file before a new file is created. Min 1 KB, max 10 GiB. The max_bytes limit may be exceeded in cases where messages are larger than the limit.
- max
Duration String - Optional. The maximum duration that can elapse before a new Cloud Storage file is created. Min 1 minute, max 10 minutes, default 5 minutes. May not exceed the subscription's acknowledgement deadline.
- state String
- An output-only field that indicates whether or not the subscription can receive messages.
- text
Config Property Map - Optional. If set, message data will be written to Cloud Storage in text format.
DeadLetterPolicyResponse
- Dead
Letter stringTopic - Optional. The name of the topic to which dead letter messages should be published. Format is
projects/{project}/topics/{topic}
.The Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Publish() to this topic. The operation will fail if the topic does not exist. Users should ensure that there is a subscription attached to this topic since messages published to a topic with no subscriptions are lost. - Max
Delivery intAttempts - Optional. The maximum number of delivery attempts for any message. The value must be between 5 and 100. The number of delivery attempts is defined as 1 + (the sum of number of NACKs and number of times the acknowledgement deadline has been exceeded for the message). A NACK is any call to ModifyAckDeadline with a 0 deadline. Note that client libraries may automatically extend ack_deadlines. This field will be honored on a best effort basis. If this parameter is 0, a default value of 5 is used.
- Dead
Letter stringTopic - Optional. The name of the topic to which dead letter messages should be published. Format is
projects/{project}/topics/{topic}
.The Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Publish() to this topic. The operation will fail if the topic does not exist. Users should ensure that there is a subscription attached to this topic since messages published to a topic with no subscriptions are lost. - Max
Delivery intAttempts - Optional. The maximum number of delivery attempts for any message. The value must be between 5 and 100. The number of delivery attempts is defined as 1 + (the sum of number of NACKs and number of times the acknowledgement deadline has been exceeded for the message). A NACK is any call to ModifyAckDeadline with a 0 deadline. Note that client libraries may automatically extend ack_deadlines. This field will be honored on a best effort basis. If this parameter is 0, a default value of 5 is used.
- dead
Letter StringTopic - Optional. The name of the topic to which dead letter messages should be published. Format is
projects/{project}/topics/{topic}
.The Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Publish() to this topic. The operation will fail if the topic does not exist. Users should ensure that there is a subscription attached to this topic since messages published to a topic with no subscriptions are lost. - max
Delivery IntegerAttempts - Optional. The maximum number of delivery attempts for any message. The value must be between 5 and 100. The number of delivery attempts is defined as 1 + (the sum of number of NACKs and number of times the acknowledgement deadline has been exceeded for the message). A NACK is any call to ModifyAckDeadline with a 0 deadline. Note that client libraries may automatically extend ack_deadlines. This field will be honored on a best effort basis. If this parameter is 0, a default value of 5 is used.
- dead
Letter stringTopic - Optional. The name of the topic to which dead letter messages should be published. Format is
projects/{project}/topics/{topic}
.The Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Publish() to this topic. The operation will fail if the topic does not exist. Users should ensure that there is a subscription attached to this topic since messages published to a topic with no subscriptions are lost. - max
Delivery numberAttempts - Optional. The maximum number of delivery attempts for any message. The value must be between 5 and 100. The number of delivery attempts is defined as 1 + (the sum of number of NACKs and number of times the acknowledgement deadline has been exceeded for the message). A NACK is any call to ModifyAckDeadline with a 0 deadline. Note that client libraries may automatically extend ack_deadlines. This field will be honored on a best effort basis. If this parameter is 0, a default value of 5 is used.
- dead_
letter_ strtopic - Optional. The name of the topic to which dead letter messages should be published. Format is
projects/{project}/topics/{topic}
.The Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Publish() to this topic. The operation will fail if the topic does not exist. Users should ensure that there is a subscription attached to this topic since messages published to a topic with no subscriptions are lost. - max_
delivery_ intattempts - Optional. The maximum number of delivery attempts for any message. The value must be between 5 and 100. The number of delivery attempts is defined as 1 + (the sum of number of NACKs and number of times the acknowledgement deadline has been exceeded for the message). A NACK is any call to ModifyAckDeadline with a 0 deadline. Note that client libraries may automatically extend ack_deadlines. This field will be honored on a best effort basis. If this parameter is 0, a default value of 5 is used.
- dead
Letter StringTopic - Optional. The name of the topic to which dead letter messages should be published. Format is
projects/{project}/topics/{topic}
.The Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have permission to Publish() to this topic. The operation will fail if the topic does not exist. Users should ensure that there is a subscription attached to this topic since messages published to a topic with no subscriptions are lost. - max
Delivery NumberAttempts - Optional. The maximum number of delivery attempts for any message. The value must be between 5 and 100. The number of delivery attempts is defined as 1 + (the sum of number of NACKs and number of times the acknowledgement deadline has been exceeded for the message). A NACK is any call to ModifyAckDeadline with a 0 deadline. Note that client libraries may automatically extend ack_deadlines. This field will be honored on a best effort basis. If this parameter is 0, a default value of 5 is used.
ExpirationPolicyResponse
- Ttl string
- Optional. Specifies the "time-to-live" duration for an associated resource. The resource expires if it is not active for a period of
ttl
. The definition of "activity" depends on the type of the associated resource. The minimum and maximum allowed values forttl
depend on the type of the associated resource, as well. Ifttl
is not set, the associated resource never expires.
- Ttl string
- Optional. Specifies the "time-to-live" duration for an associated resource. The resource expires if it is not active for a period of
ttl
. The definition of "activity" depends on the type of the associated resource. The minimum and maximum allowed values forttl
depend on the type of the associated resource, as well. Ifttl
is not set, the associated resource never expires.
- ttl String
- Optional. Specifies the "time-to-live" duration for an associated resource. The resource expires if it is not active for a period of
ttl
. The definition of "activity" depends on the type of the associated resource. The minimum and maximum allowed values forttl
depend on the type of the associated resource, as well. Ifttl
is not set, the associated resource never expires.
- ttl string
- Optional. Specifies the "time-to-live" duration for an associated resource. The resource expires if it is not active for a period of
ttl
. The definition of "activity" depends on the type of the associated resource. The minimum and maximum allowed values forttl
depend on the type of the associated resource, as well. Ifttl
is not set, the associated resource never expires.
- ttl str
- Optional. Specifies the "time-to-live" duration for an associated resource. The resource expires if it is not active for a period of
ttl
. The definition of "activity" depends on the type of the associated resource. The minimum and maximum allowed values forttl
depend on the type of the associated resource, as well. Ifttl
is not set, the associated resource never expires.
- ttl String
- Optional. Specifies the "time-to-live" duration for an associated resource. The resource expires if it is not active for a period of
ttl
. The definition of "activity" depends on the type of the associated resource. The minimum and maximum allowed values forttl
depend on the type of the associated resource, as well. Ifttl
is not set, the associated resource never expires.
NoWrapperResponse
- Write
Metadata bool - Optional. When true, writes the Pub/Sub message metadata to
x-goog-pubsub-:
headers of the HTTP request. Writes the Pub/Sub message attributes to:
headers of the HTTP request.
- Write
Metadata bool - Optional. When true, writes the Pub/Sub message metadata to
x-goog-pubsub-:
headers of the HTTP request. Writes the Pub/Sub message attributes to:
headers of the HTTP request.
- write
Metadata Boolean - Optional. When true, writes the Pub/Sub message metadata to
x-goog-pubsub-:
headers of the HTTP request. Writes the Pub/Sub message attributes to:
headers of the HTTP request.
- write
Metadata boolean - Optional. When true, writes the Pub/Sub message metadata to
x-goog-pubsub-:
headers of the HTTP request. Writes the Pub/Sub message attributes to:
headers of the HTTP request.
- write_
metadata bool - Optional. When true, writes the Pub/Sub message metadata to
x-goog-pubsub-:
headers of the HTTP request. Writes the Pub/Sub message attributes to:
headers of the HTTP request.
- write
Metadata Boolean - Optional. When true, writes the Pub/Sub message metadata to
x-goog-pubsub-:
headers of the HTTP request. Writes the Pub/Sub message attributes to:
headers of the HTTP request.
OidcTokenResponse
- Audience string
- Optional. Audience to be used when generating OIDC token. The audience claim identifies the recipients that the JWT is intended for. The audience value is a single case-sensitive string. Having multiple values (array) for the audience field is not supported. More info about the OIDC JWT token audience here: https://tools.ietf.org/html/rfc7519#section-4.1.3 Note: if not specified, the Push endpoint URL will be used.
- Service
Account stringEmail - Optional. Service account email used for generating the OIDC token. For more information on setting up authentication, see Push subscriptions.
- Audience string
- Optional. Audience to be used when generating OIDC token. The audience claim identifies the recipients that the JWT is intended for. The audience value is a single case-sensitive string. Having multiple values (array) for the audience field is not supported. More info about the OIDC JWT token audience here: https://tools.ietf.org/html/rfc7519#section-4.1.3 Note: if not specified, the Push endpoint URL will be used.
- Service
Account stringEmail - Optional. Service account email used for generating the OIDC token. For more information on setting up authentication, see Push subscriptions.
- audience String
- Optional. Audience to be used when generating OIDC token. The audience claim identifies the recipients that the JWT is intended for. The audience value is a single case-sensitive string. Having multiple values (array) for the audience field is not supported. More info about the OIDC JWT token audience here: https://tools.ietf.org/html/rfc7519#section-4.1.3 Note: if not specified, the Push endpoint URL will be used.
- service
Account StringEmail - Optional. Service account email used for generating the OIDC token. For more information on setting up authentication, see Push subscriptions.
- audience string
- Optional. Audience to be used when generating OIDC token. The audience claim identifies the recipients that the JWT is intended for. The audience value is a single case-sensitive string. Having multiple values (array) for the audience field is not supported. More info about the OIDC JWT token audience here: https://tools.ietf.org/html/rfc7519#section-4.1.3 Note: if not specified, the Push endpoint URL will be used.
- service
Account stringEmail - Optional. Service account email used for generating the OIDC token. For more information on setting up authentication, see Push subscriptions.
- audience str
- Optional. Audience to be used when generating OIDC token. The audience claim identifies the recipients that the JWT is intended for. The audience value is a single case-sensitive string. Having multiple values (array) for the audience field is not supported. More info about the OIDC JWT token audience here: https://tools.ietf.org/html/rfc7519#section-4.1.3 Note: if not specified, the Push endpoint URL will be used.
- service_
account_ stremail - Optional. Service account email used for generating the OIDC token. For more information on setting up authentication, see Push subscriptions.
- audience String
- Optional. Audience to be used when generating OIDC token. The audience claim identifies the recipients that the JWT is intended for. The audience value is a single case-sensitive string. Having multiple values (array) for the audience field is not supported. More info about the OIDC JWT token audience here: https://tools.ietf.org/html/rfc7519#section-4.1.3 Note: if not specified, the Push endpoint URL will be used.
- service
Account StringEmail - Optional. Service account email used for generating the OIDC token. For more information on setting up authentication, see Push subscriptions.
PushConfigResponse
- Attributes Dictionary<string, string>
- Optional. Endpoint configuration attributes that can be used to control different aspects of the message delivery. The only currently supported attribute is
x-goog-version
, which you can use to change the format of the pushed message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the pushed message (i.e., its fields and metadata). If not present during theCreateSubscription
call, it will default to the version of the Pub/Sub API used to make such call. If not present in aModifyPushConfig
call, its value will not be changed.GetSubscription
calls will always return a valid version, even if the subscription was created without this attribute. The only supported values for thex-goog-version
attribute are: *v1beta1
: uses the push format defined in the v1beta1 Pub/Sub API. *v1
orv1beta2
: uses the push format defined in the v1 Pub/Sub API. For example:attributes { "x-goog-version": "v1" }
- No
Wrapper Pulumi.Google Native. Pubsub. V1. Inputs. No Wrapper Response - Optional. When set, the payload to the push endpoint is not wrapped.
- Oidc
Token Pulumi.Google Native. Pubsub. V1. Inputs. Oidc Token Response - Optional. If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - Pubsub
Wrapper Pulumi.Google Native. Pubsub. V1. Inputs. Pubsub Wrapper Response - Optional. When set, the payload to the push endpoint is in the form of the JSON representation of a PubsubMessage (https://cloud.google.com/pubsub/docs/reference/rpc/google.pubsub.v1#pubsubmessage).
- Push
Endpoint string - Optional. A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use
https://example.com/push
.
- Attributes map[string]string
- Optional. Endpoint configuration attributes that can be used to control different aspects of the message delivery. The only currently supported attribute is
x-goog-version
, which you can use to change the format of the pushed message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the pushed message (i.e., its fields and metadata). If not present during theCreateSubscription
call, it will default to the version of the Pub/Sub API used to make such call. If not present in aModifyPushConfig
call, its value will not be changed.GetSubscription
calls will always return a valid version, even if the subscription was created without this attribute. The only supported values for thex-goog-version
attribute are: *v1beta1
: uses the push format defined in the v1beta1 Pub/Sub API. *v1
orv1beta2
: uses the push format defined in the v1 Pub/Sub API. For example:attributes { "x-goog-version": "v1" }
- No
Wrapper NoWrapper Response - Optional. When set, the payload to the push endpoint is not wrapped.
- Oidc
Token OidcToken Response - Optional. If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - Pubsub
Wrapper PubsubWrapper Response - Optional. When set, the payload to the push endpoint is in the form of the JSON representation of a PubsubMessage (https://cloud.google.com/pubsub/docs/reference/rpc/google.pubsub.v1#pubsubmessage).
- Push
Endpoint string - Optional. A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use
https://example.com/push
.
- attributes Map<String,String>
- Optional. Endpoint configuration attributes that can be used to control different aspects of the message delivery. The only currently supported attribute is
x-goog-version
, which you can use to change the format of the pushed message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the pushed message (i.e., its fields and metadata). If not present during theCreateSubscription
call, it will default to the version of the Pub/Sub API used to make such call. If not present in aModifyPushConfig
call, its value will not be changed.GetSubscription
calls will always return a valid version, even if the subscription was created without this attribute. The only supported values for thex-goog-version
attribute are: *v1beta1
: uses the push format defined in the v1beta1 Pub/Sub API. *v1
orv1beta2
: uses the push format defined in the v1 Pub/Sub API. For example:attributes { "x-goog-version": "v1" }
- no
Wrapper NoWrapper Response - Optional. When set, the payload to the push endpoint is not wrapped.
- oidc
Token OidcToken Response - Optional. If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - pubsub
Wrapper PubsubWrapper Response - Optional. When set, the payload to the push endpoint is in the form of the JSON representation of a PubsubMessage (https://cloud.google.com/pubsub/docs/reference/rpc/google.pubsub.v1#pubsubmessage).
- push
Endpoint String - Optional. A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use
https://example.com/push
.
- attributes {[key: string]: string}
- Optional. Endpoint configuration attributes that can be used to control different aspects of the message delivery. The only currently supported attribute is
x-goog-version
, which you can use to change the format of the pushed message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the pushed message (i.e., its fields and metadata). If not present during theCreateSubscription
call, it will default to the version of the Pub/Sub API used to make such call. If not present in aModifyPushConfig
call, its value will not be changed.GetSubscription
calls will always return a valid version, even if the subscription was created without this attribute. The only supported values for thex-goog-version
attribute are: *v1beta1
: uses the push format defined in the v1beta1 Pub/Sub API. *v1
orv1beta2
: uses the push format defined in the v1 Pub/Sub API. For example:attributes { "x-goog-version": "v1" }
- no
Wrapper NoWrapper Response - Optional. When set, the payload to the push endpoint is not wrapped.
- oidc
Token OidcToken Response - Optional. If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - pubsub
Wrapper PubsubWrapper Response - Optional. When set, the payload to the push endpoint is in the form of the JSON representation of a PubsubMessage (https://cloud.google.com/pubsub/docs/reference/rpc/google.pubsub.v1#pubsubmessage).
- push
Endpoint string - Optional. A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use
https://example.com/push
.
- attributes Mapping[str, str]
- Optional. Endpoint configuration attributes that can be used to control different aspects of the message delivery. The only currently supported attribute is
x-goog-version
, which you can use to change the format of the pushed message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the pushed message (i.e., its fields and metadata). If not present during theCreateSubscription
call, it will default to the version of the Pub/Sub API used to make such call. If not present in aModifyPushConfig
call, its value will not be changed.GetSubscription
calls will always return a valid version, even if the subscription was created without this attribute. The only supported values for thex-goog-version
attribute are: *v1beta1
: uses the push format defined in the v1beta1 Pub/Sub API. *v1
orv1beta2
: uses the push format defined in the v1 Pub/Sub API. For example:attributes { "x-goog-version": "v1" }
- no_
wrapper NoWrapper Response - Optional. When set, the payload to the push endpoint is not wrapped.
- oidc_
token OidcToken Response - Optional. If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - pubsub_
wrapper PubsubWrapper Response - Optional. When set, the payload to the push endpoint is in the form of the JSON representation of a PubsubMessage (https://cloud.google.com/pubsub/docs/reference/rpc/google.pubsub.v1#pubsubmessage).
- push_
endpoint str - Optional. A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use
https://example.com/push
.
- attributes Map<String>
- Optional. Endpoint configuration attributes that can be used to control different aspects of the message delivery. The only currently supported attribute is
x-goog-version
, which you can use to change the format of the pushed message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the pushed message (i.e., its fields and metadata). If not present during theCreateSubscription
call, it will default to the version of the Pub/Sub API used to make such call. If not present in aModifyPushConfig
call, its value will not be changed.GetSubscription
calls will always return a valid version, even if the subscription was created without this attribute. The only supported values for thex-goog-version
attribute are: *v1beta1
: uses the push format defined in the v1beta1 Pub/Sub API. *v1
orv1beta2
: uses the push format defined in the v1 Pub/Sub API. For example:attributes { "x-goog-version": "v1" }
- no
Wrapper Property Map - Optional. When set, the payload to the push endpoint is not wrapped.
- oidc
Token Property Map - Optional. If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - pubsub
Wrapper Property Map - Optional. When set, the payload to the push endpoint is in the form of the JSON representation of a PubsubMessage (https://cloud.google.com/pubsub/docs/reference/rpc/google.pubsub.v1#pubsubmessage).
- push
Endpoint String - Optional. A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use
https://example.com/push
.
RetryPolicyResponse
- Maximum
Backoff string - Optional. The maximum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 600 seconds.
- Minimum
Backoff string - Optional. The minimum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 10 seconds.
- Maximum
Backoff string - Optional. The maximum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 600 seconds.
- Minimum
Backoff string - Optional. The minimum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 10 seconds.
- maximum
Backoff String - Optional. The maximum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 600 seconds.
- minimum
Backoff String - Optional. The minimum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 10 seconds.
- maximum
Backoff string - Optional. The maximum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 600 seconds.
- minimum
Backoff string - Optional. The minimum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 10 seconds.
- maximum_
backoff str - Optional. The maximum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 600 seconds.
- minimum_
backoff str - Optional. The minimum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 10 seconds.
- maximum
Backoff String - Optional. The maximum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 600 seconds.
- minimum
Backoff String - Optional. The minimum delay between consecutive deliveries of a given message. Value should be between 0 and 600 seconds. Defaults to 10 seconds.
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi