public interface PushConfigOrBuilder
extends com.google.protobuf.MessageOrBuilder
| Modifier and Type | Method and Description |
|---|---|
boolean |
containsAttributes(String key)
Endpoint configuration attributes that can be used to control different
aspects of the message delivery.
|
Map<String,String> |
getAttributes()
Deprecated.
|
int |
getAttributesCount()
Endpoint configuration attributes that can be used to control different
aspects of the message delivery.
|
Map<String,String> |
getAttributesMap()
Endpoint configuration attributes that can be used to control different
aspects of the message delivery.
|
String |
getAttributesOrDefault(String key,
String defaultValue)
Endpoint configuration attributes that can be used to control different
aspects of the message delivery.
|
String |
getAttributesOrThrow(String key)
Endpoint configuration attributes that can be used to control different
aspects of the message delivery.
|
PushConfig.AuthenticationMethodCase |
getAuthenticationMethodCase() |
PushConfig.OidcToken |
getOidcToken()
If specified, Pub/Sub will generate and attach an OIDC JWT token as an
`Authorization` header in the HTTP request for every pushed message.
|
PushConfig.OidcTokenOrBuilder |
getOidcTokenOrBuilder()
If specified, Pub/Sub will generate and attach an OIDC JWT token as an
`Authorization` header in the HTTP request for every pushed message.
|
String |
getPushEndpoint()
A URL locating the endpoint to which messages should be pushed.
|
com.google.protobuf.ByteString |
getPushEndpointBytes()
A URL locating the endpoint to which messages should be pushed.
|
boolean |
hasOidcToken()
If specified, Pub/Sub will generate and attach an OIDC JWT token as an
`Authorization` header in the HTTP request for every pushed message.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofString getPushEndpoint()
A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use `https://example.com/push`.
string push_endpoint = 1;com.google.protobuf.ByteString getPushEndpointBytes()
A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use `https://example.com/push`.
string push_endpoint = 1;int getAttributesCount()
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 the `CreateSubscription` call, it will default to
the version of the Pub/Sub API used to make such call. If not present in a
`ModifyPushConfig` 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 the `x-goog-version` attribute are:
* `v1beta1`: uses the push format defined in the v1beta1 Pub/Sub API.
* `v1` or `v1beta2`: uses the push format defined in the v1 Pub/Sub API.
For example:
<pre><code>attributes { "x-goog-version": "v1" } </code></pre>
map<string, string> attributes = 2;boolean containsAttributes(String key)
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 the `CreateSubscription` call, it will default to
the version of the Pub/Sub API used to make such call. If not present in a
`ModifyPushConfig` 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 the `x-goog-version` attribute are:
* `v1beta1`: uses the push format defined in the v1beta1 Pub/Sub API.
* `v1` or `v1beta2`: uses the push format defined in the v1 Pub/Sub API.
For example:
<pre><code>attributes { "x-goog-version": "v1" } </code></pre>
map<string, string> attributes = 2;@Deprecated Map<String,String> getAttributes()
getAttributesMap() instead.Map<String,String> getAttributesMap()
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 the `CreateSubscription` call, it will default to
the version of the Pub/Sub API used to make such call. If not present in a
`ModifyPushConfig` 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 the `x-goog-version` attribute are:
* `v1beta1`: uses the push format defined in the v1beta1 Pub/Sub API.
* `v1` or `v1beta2`: uses the push format defined in the v1 Pub/Sub API.
For example:
<pre><code>attributes { "x-goog-version": "v1" } </code></pre>
map<string, string> attributes = 2;String getAttributesOrDefault(String key, String defaultValue)
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 the `CreateSubscription` call, it will default to
the version of the Pub/Sub API used to make such call. If not present in a
`ModifyPushConfig` 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 the `x-goog-version` attribute are:
* `v1beta1`: uses the push format defined in the v1beta1 Pub/Sub API.
* `v1` or `v1beta2`: uses the push format defined in the v1 Pub/Sub API.
For example:
<pre><code>attributes { "x-goog-version": "v1" } </code></pre>
map<string, string> attributes = 2;String getAttributesOrThrow(String key)
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 the `CreateSubscription` call, it will default to
the version of the Pub/Sub API used to make such call. If not present in a
`ModifyPushConfig` 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 the `x-goog-version` attribute are:
* `v1beta1`: uses the push format defined in the v1beta1 Pub/Sub API.
* `v1` or `v1beta2`: uses the push format defined in the v1 Pub/Sub API.
For example:
<pre><code>attributes { "x-goog-version": "v1" } </code></pre>
map<string, string> attributes = 2;boolean hasOidcToken()
If specified, Pub/Sub will generate and attach an OIDC JWT token as an `Authorization` header in the HTTP request for every pushed message.
.google.pubsub.v1.PushConfig.OidcToken oidc_token = 3;PushConfig.OidcToken getOidcToken()
If specified, Pub/Sub will generate and attach an OIDC JWT token as an `Authorization` header in the HTTP request for every pushed message.
.google.pubsub.v1.PushConfig.OidcToken oidc_token = 3;PushConfig.OidcTokenOrBuilder getOidcTokenOrBuilder()
If specified, Pub/Sub will generate and attach an OIDC JWT token as an `Authorization` header in the HTTP request for every pushed message.
.google.pubsub.v1.PushConfig.OidcToken oidc_token = 3;PushConfig.AuthenticationMethodCase getAuthenticationMethodCase()
Copyright © 2020 Google LLC. All rights reserved.