Google Cloud Native is in preview. Google Cloud Classic is fully supported.
google-native.pubsub/v1beta2.Subscription
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Creates a subscription to a given topic. If the subscription already exists, returns ALREADY_EXISTS
. If the corresponding topic doesn’t exist, returns NOT_FOUND
. If the name is not provided in the request, the server will assign a random name for this subscription on the same project as the topic. Note that for REST API requests, you must specify a name.
Create Subscription Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Subscription(name: string, args: SubscriptionArgs, opts?: CustomResourceOptions);
@overload
def Subscription(resource_name: str,
args: SubscriptionArgs,
opts: Optional[ResourceOptions] = None)
@overload
def Subscription(resource_name: str,
opts: Optional[ResourceOptions] = None,
subscription_id: Optional[str] = None,
ack_deadline_seconds: Optional[int] = None,
name: Optional[str] = None,
project: Optional[str] = None,
push_config: Optional[PushConfigArgs] = None,
topic: Optional[str] = None)
func NewSubscription(ctx *Context, name string, args SubscriptionArgs, opts ...ResourceOption) (*Subscription, error)
public Subscription(string name, SubscriptionArgs args, CustomResourceOptions? opts = null)
public Subscription(String name, SubscriptionArgs args)
public Subscription(String name, SubscriptionArgs args, CustomResourceOptions options)
type: google-native:pubsub/v1beta2:Subscription
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args SubscriptionArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args SubscriptionArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args SubscriptionArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args SubscriptionArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args SubscriptionArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var examplesubscriptionResourceResourceFromPubsubv1beta2 = new GoogleNative.Pubsub.V1Beta2.Subscription("examplesubscriptionResourceResourceFromPubsubv1beta2", new()
{
SubscriptionId = "string",
AckDeadlineSeconds = 0,
Name = "string",
Project = "string",
PushConfig = new GoogleNative.Pubsub.V1Beta2.Inputs.PushConfigArgs
{
Attributes =
{
{ "string", "string" },
},
OidcToken = new GoogleNative.Pubsub.V1Beta2.Inputs.OidcTokenArgs
{
Audience = "string",
ServiceAccountEmail = "string",
},
PushEndpoint = "string",
},
Topic = "string",
});
example, err := pubsubv1beta2.NewSubscription(ctx, "examplesubscriptionResourceResourceFromPubsubv1beta2", &pubsubv1beta2.SubscriptionArgs{
SubscriptionId: pulumi.String("string"),
AckDeadlineSeconds: pulumi.Int(0),
Name: pulumi.String("string"),
Project: pulumi.String("string"),
PushConfig: &pubsub.PushConfigArgs{
Attributes: pulumi.StringMap{
"string": pulumi.String("string"),
},
OidcToken: &pubsub.OidcTokenArgs{
Audience: pulumi.String("string"),
ServiceAccountEmail: pulumi.String("string"),
},
PushEndpoint: pulumi.String("string"),
},
Topic: pulumi.String("string"),
})
var examplesubscriptionResourceResourceFromPubsubv1beta2 = new Subscription("examplesubscriptionResourceResourceFromPubsubv1beta2", SubscriptionArgs.builder()
.subscriptionId("string")
.ackDeadlineSeconds(0)
.name("string")
.project("string")
.pushConfig(PushConfigArgs.builder()
.attributes(Map.of("string", "string"))
.oidcToken(OidcTokenArgs.builder()
.audience("string")
.serviceAccountEmail("string")
.build())
.pushEndpoint("string")
.build())
.topic("string")
.build());
examplesubscription_resource_resource_from_pubsubv1beta2 = google_native.pubsub.v1beta2.Subscription("examplesubscriptionResourceResourceFromPubsubv1beta2",
subscription_id="string",
ack_deadline_seconds=0,
name="string",
project="string",
push_config=google_native.pubsub.v1beta2.PushConfigArgs(
attributes={
"string": "string",
},
oidc_token=google_native.pubsub.v1beta2.OidcTokenArgs(
audience="string",
service_account_email="string",
),
push_endpoint="string",
),
topic="string")
const examplesubscriptionResourceResourceFromPubsubv1beta2 = new google_native.pubsub.v1beta2.Subscription("examplesubscriptionResourceResourceFromPubsubv1beta2", {
subscriptionId: "string",
ackDeadlineSeconds: 0,
name: "string",
project: "string",
pushConfig: {
attributes: {
string: "string",
},
oidcToken: {
audience: "string",
serviceAccountEmail: "string",
},
pushEndpoint: "string",
},
topic: "string",
});
type: google-native:pubsub/v1beta2:Subscription
properties:
ackDeadlineSeconds: 0
name: string
project: string
pushConfig:
attributes:
string: string
oidcToken:
audience: string
serviceAccountEmail: string
pushEndpoint: string
subscriptionId: string
topic: string
Subscription Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The Subscription resource accepts the following input properties:
- Subscription
Id string - Ack
Deadline intSeconds - This value is the maximum time after a subscriber receives a message before the subscriber should acknowledge the message. After message delivery but before the ack deadline expires and before the message is acknowledged, it is an outstanding message and will not be delivered again during that time (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 pull. The maximum custom deadline you can specify is 600 seconds (10 minutes). 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. If this parameter is 0, a default value of 10 seconds is used. - 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"
. - Project string
- Push
Config Pulumi.Google Native. Pubsub. V1Beta2. Inputs. Push Config - 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. - Topic string
- The name of the topic from which this subscription is receiving messages. The value of this field will be
_deleted-topic_
if the topic has been deleted.
- Subscription
Id string - Ack
Deadline intSeconds - This value is the maximum time after a subscriber receives a message before the subscriber should acknowledge the message. After message delivery but before the ack deadline expires and before the message is acknowledged, it is an outstanding message and will not be delivered again during that time (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 pull. The maximum custom deadline you can specify is 600 seconds (10 minutes). 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. If this parameter is 0, a default value of 10 seconds is used. - 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"
. - Project string
- Push
Config PushConfig Args - 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. - Topic string
- The name of the topic from which this subscription is receiving messages. The value of this field will be
_deleted-topic_
if the topic has been deleted.
- subscription
Id String - ack
Deadline IntegerSeconds - This value is the maximum time after a subscriber receives a message before the subscriber should acknowledge the message. After message delivery but before the ack deadline expires and before the message is acknowledged, it is an outstanding message and will not be delivered again during that time (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 pull. The maximum custom deadline you can specify is 600 seconds (10 minutes). 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. If this parameter is 0, a default value of 10 seconds is used. - 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"
. - project String
- push
Config PushConfig - 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. - topic String
- The name of the topic from which this subscription is receiving messages. The value of this field will be
_deleted-topic_
if the topic has been deleted.
- subscription
Id string - ack
Deadline numberSeconds - This value is the maximum time after a subscriber receives a message before the subscriber should acknowledge the message. After message delivery but before the ack deadline expires and before the message is acknowledged, it is an outstanding message and will not be delivered again during that time (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 pull. The maximum custom deadline you can specify is 600 seconds (10 minutes). 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. If this parameter is 0, a default value of 10 seconds is used. - 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"
. - project string
- push
Config PushConfig - 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. - topic string
- The name of the topic from which this subscription is receiving messages. The value of this field will be
_deleted-topic_
if the topic has been deleted.
- subscription_
id str - ack_
deadline_ intseconds - This value is the maximum time after a subscriber receives a message before the subscriber should acknowledge the message. After message delivery but before the ack deadline expires and before the message is acknowledged, it is an outstanding message and will not be delivered again during that time (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 pull. The maximum custom deadline you can specify is 600 seconds (10 minutes). 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. If this parameter is 0, a default value of 10 seconds is used. - 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"
. - project str
- push_
config PushConfig Args - 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. - topic str
- The name of the topic from which this subscription is receiving messages. The value of this field will be
_deleted-topic_
if the topic has been deleted.
- subscription
Id String - ack
Deadline NumberSeconds - This value is the maximum time after a subscriber receives a message before the subscriber should acknowledge the message. After message delivery but before the ack deadline expires and before the message is acknowledged, it is an outstanding message and will not be delivered again during that time (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 pull. The maximum custom deadline you can specify is 600 seconds (10 minutes). 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. If this parameter is 0, a default value of 10 seconds is used. - 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"
. - project String
- push
Config Property Map - 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. - topic String
- The name of the topic from which this subscription is receiving messages. The value of this field will be
_deleted-topic_
if the topic has been deleted.
Outputs
All input properties are implicitly available as output properties. Additionally, the Subscription resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Supporting Types
OidcToken, OidcTokenArgs
- Audience string
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- Audience string
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience String
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience string
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience str
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience String
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
OidcTokenResponse, OidcTokenResponseArgs
- Audience string
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- Audience string
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience String
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience string
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience str
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
- audience String
- 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 - Service account email to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.
PushConfig, PushConfigArgs
- Attributes Dictionary<string, string>
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - Oidc
Token Pulumi.Google Native. Pubsub. V1Beta2. Inputs. Oidc Token - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - Push
Endpoint string - 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
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - Oidc
Token OidcToken - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - Push
Endpoint string - 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>
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc
Token OidcToken - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push
Endpoint String - 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}
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc
Token OidcToken - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push
Endpoint string - 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]
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc_
token OidcToken - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push_
endpoint str - 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>
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc
Token Property Map - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push
Endpoint String - A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use "https://example.com/push".
PushConfigResponse, PushConfigResponseArgs
- Attributes Dictionary<string, string>
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - Oidc
Token Pulumi.Google Native. Pubsub. V1Beta2. Inputs. Oidc Token Response - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - Push
Endpoint string - 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
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - Oidc
Token OidcToken Response - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - Push
Endpoint string - 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>
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc
Token OidcToken Response - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push
Endpoint String - 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}
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc
Token OidcToken Response - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push
Endpoint string - 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]
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc_
token OidcToken Response - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push_
endpoint str - 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>
- Endpoint configuration attributes. Every endpoint has a set of API supported attributes that can be used to control different aspects of the message delivery. The currently supported attribute is
x-goog-version
, which you can use to change the format of the push message. This attribute indicates the version of the data expected by the endpoint. This controls the shape of the envelope (i.e. its fields and metadata). The endpoint version is based on the version of the Pub/Sub API. If not present during theCreateSubscription
call, it will default to the version of the API used to make such call. If not present during 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 possible values for this 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. - oidc
Token Property Map - If specified, Pub/Sub will generate and attach an OIDC JWT token as an
Authorization
header in the HTTP request for every pushed message. - push
Endpoint String - A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use "https://example.com/push".
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.