#[non_exhaustive]pub struct PublishBatchRequestEntryBuilder { /* private fields */ }Expand description
A builder for PublishBatchRequestEntry.
Implementations§
source§impl PublishBatchRequestEntryBuilder
impl PublishBatchRequestEntryBuilder
sourcepub fn id(self, input: impl Into<String>) -> Self
pub fn id(self, input: impl Into<String>) -> Self
An identifier for the message in this batch.
The Ids of a batch request must be unique within a request.
This identifier can have up to 80 characters. The following characters are accepted: alphanumeric characters, hyphens(-), and underscores (_).
sourcepub fn set_id(self, input: Option<String>) -> Self
pub fn set_id(self, input: Option<String>) -> Self
An identifier for the message in this batch.
The Ids of a batch request must be unique within a request.
This identifier can have up to 80 characters. The following characters are accepted: alphanumeric characters, hyphens(-), and underscores (_).
sourcepub fn get_id(&self) -> &Option<String>
pub fn get_id(&self) -> &Option<String>
An identifier for the message in this batch.
The Ids of a batch request must be unique within a request.
This identifier can have up to 80 characters. The following characters are accepted: alphanumeric characters, hyphens(-), and underscores (_).
sourcepub fn message(self, input: impl Into<String>) -> Self
pub fn message(self, input: impl Into<String>) -> Self
The body of the message.
This field is required.sourcepub fn set_message(self, input: Option<String>) -> Self
pub fn set_message(self, input: Option<String>) -> Self
The body of the message.
sourcepub fn get_message(&self) -> &Option<String>
pub fn get_message(&self) -> &Option<String>
The body of the message.
sourcepub fn set_subject(self, input: Option<String>) -> Self
pub fn set_subject(self, input: Option<String>) -> Self
The subject of the batch message.
sourcepub fn get_subject(&self) -> &Option<String>
pub fn get_subject(&self) -> &Option<String>
The subject of the batch message.
sourcepub fn message_structure(self, input: impl Into<String>) -> Self
pub fn message_structure(self, input: impl Into<String>) -> Self
Set MessageStructure to json if you want to send a different message for each protocol. For example, using one publish action, you can send a short message to your SMS subscribers and a longer message to your email subscribers. If you set MessageStructure to json, the value of the Message parameter must:
-
be a syntactically valid JSON object; and
-
contain at least a top-level JSON key of "default" with a value that is a string.
You can define other top-level keys that define the message you want to send to a specific transport protocol (e.g. http).
sourcepub fn set_message_structure(self, input: Option<String>) -> Self
pub fn set_message_structure(self, input: Option<String>) -> Self
Set MessageStructure to json if you want to send a different message for each protocol. For example, using one publish action, you can send a short message to your SMS subscribers and a longer message to your email subscribers. If you set MessageStructure to json, the value of the Message parameter must:
-
be a syntactically valid JSON object; and
-
contain at least a top-level JSON key of "default" with a value that is a string.
You can define other top-level keys that define the message you want to send to a specific transport protocol (e.g. http).
sourcepub fn get_message_structure(&self) -> &Option<String>
pub fn get_message_structure(&self) -> &Option<String>
Set MessageStructure to json if you want to send a different message for each protocol. For example, using one publish action, you can send a short message to your SMS subscribers and a longer message to your email subscribers. If you set MessageStructure to json, the value of the Message parameter must:
-
be a syntactically valid JSON object; and
-
contain at least a top-level JSON key of "default" with a value that is a string.
You can define other top-level keys that define the message you want to send to a specific transport protocol (e.g. http).
sourcepub fn message_attributes(
self,
k: impl Into<String>,
v: MessageAttributeValue
) -> Self
pub fn message_attributes( self, k: impl Into<String>, v: MessageAttributeValue ) -> Self
Adds a key-value pair to message_attributes.
To override the contents of this collection use set_message_attributes.
Each message attribute consists of a Name, Type, and Value. For more information, see Amazon SNS message attributes in the Amazon SNS Developer Guide.
sourcepub fn set_message_attributes(
self,
input: Option<HashMap<String, MessageAttributeValue>>
) -> Self
pub fn set_message_attributes( self, input: Option<HashMap<String, MessageAttributeValue>> ) -> Self
Each message attribute consists of a Name, Type, and Value. For more information, see Amazon SNS message attributes in the Amazon SNS Developer Guide.
sourcepub fn get_message_attributes(
&self
) -> &Option<HashMap<String, MessageAttributeValue>>
pub fn get_message_attributes( &self ) -> &Option<HashMap<String, MessageAttributeValue>>
Each message attribute consists of a Name, Type, and Value. For more information, see Amazon SNS message attributes in the Amazon SNS Developer Guide.
sourcepub fn message_deduplication_id(self, input: impl Into<String>) -> Self
pub fn message_deduplication_id(self, input: impl Into<String>) -> Self
This parameter applies only to FIFO (first-in-first-out) topics.
The token used for deduplication of messages within a 5-minute minimum deduplication interval. If a message with a particular MessageDeduplicationId is sent successfully, subsequent messages with the same MessageDeduplicationId are accepted successfully but aren't delivered.
-
Every message must have a unique
MessageDeduplicationId.-
You may provide a
MessageDeduplicationIdexplicitly. -
If you aren't able to provide a
MessageDeduplicationIdand you enableContentBasedDeduplicationfor your topic, Amazon SNS uses a SHA-256 hash to generate theMessageDeduplicationIdusing the body of the message (but not the attributes of the message). -
If you don't provide a
MessageDeduplicationIdand the topic doesn't haveContentBasedDeduplicationset, the action fails with an error. -
If the topic has a
ContentBasedDeduplicationset, yourMessageDeduplicationIdoverrides the generated one.
-
-
When
ContentBasedDeduplicationis in effect, messages with identical content sent within the deduplication interval are treated as duplicates and only one copy of the message is delivered. -
If you send one message with
ContentBasedDeduplicationenabled, and then another message with aMessageDeduplicationIdthat is the same as the one generated for the firstMessageDeduplicationId, the two messages are treated as duplicates and only one copy of the message is delivered.
The MessageDeduplicationId is available to the consumer of the message (this can be useful for troubleshooting delivery issues).
If a message is sent successfully but the acknowledgement is lost and the message is resent with the same MessageDeduplicationId after the deduplication interval, Amazon SNS can't detect duplicate messages.
Amazon SNS continues to keep track of the message deduplication ID even after the message is received and deleted.
The length of MessageDeduplicationId is 128 characters.
MessageDeduplicationId can contain alphanumeric characters (a-z, A-Z, 0-9) and punctuation (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~).
sourcepub fn set_message_deduplication_id(self, input: Option<String>) -> Self
pub fn set_message_deduplication_id(self, input: Option<String>) -> Self
This parameter applies only to FIFO (first-in-first-out) topics.
The token used for deduplication of messages within a 5-minute minimum deduplication interval. If a message with a particular MessageDeduplicationId is sent successfully, subsequent messages with the same MessageDeduplicationId are accepted successfully but aren't delivered.
-
Every message must have a unique
MessageDeduplicationId.-
You may provide a
MessageDeduplicationIdexplicitly. -
If you aren't able to provide a
MessageDeduplicationIdand you enableContentBasedDeduplicationfor your topic, Amazon SNS uses a SHA-256 hash to generate theMessageDeduplicationIdusing the body of the message (but not the attributes of the message). -
If you don't provide a
MessageDeduplicationIdand the topic doesn't haveContentBasedDeduplicationset, the action fails with an error. -
If the topic has a
ContentBasedDeduplicationset, yourMessageDeduplicationIdoverrides the generated one.
-
-
When
ContentBasedDeduplicationis in effect, messages with identical content sent within the deduplication interval are treated as duplicates and only one copy of the message is delivered. -
If you send one message with
ContentBasedDeduplicationenabled, and then another message with aMessageDeduplicationIdthat is the same as the one generated for the firstMessageDeduplicationId, the two messages are treated as duplicates and only one copy of the message is delivered.
The MessageDeduplicationId is available to the consumer of the message (this can be useful for troubleshooting delivery issues).
If a message is sent successfully but the acknowledgement is lost and the message is resent with the same MessageDeduplicationId after the deduplication interval, Amazon SNS can't detect duplicate messages.
Amazon SNS continues to keep track of the message deduplication ID even after the message is received and deleted.
The length of MessageDeduplicationId is 128 characters.
MessageDeduplicationId can contain alphanumeric characters (a-z, A-Z, 0-9) and punctuation (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~).
sourcepub fn get_message_deduplication_id(&self) -> &Option<String>
pub fn get_message_deduplication_id(&self) -> &Option<String>
This parameter applies only to FIFO (first-in-first-out) topics.
The token used for deduplication of messages within a 5-minute minimum deduplication interval. If a message with a particular MessageDeduplicationId is sent successfully, subsequent messages with the same MessageDeduplicationId are accepted successfully but aren't delivered.
-
Every message must have a unique
MessageDeduplicationId.-
You may provide a
MessageDeduplicationIdexplicitly. -
If you aren't able to provide a
MessageDeduplicationIdand you enableContentBasedDeduplicationfor your topic, Amazon SNS uses a SHA-256 hash to generate theMessageDeduplicationIdusing the body of the message (but not the attributes of the message). -
If you don't provide a
MessageDeduplicationIdand the topic doesn't haveContentBasedDeduplicationset, the action fails with an error. -
If the topic has a
ContentBasedDeduplicationset, yourMessageDeduplicationIdoverrides the generated one.
-
-
When
ContentBasedDeduplicationis in effect, messages with identical content sent within the deduplication interval are treated as duplicates and only one copy of the message is delivered. -
If you send one message with
ContentBasedDeduplicationenabled, and then another message with aMessageDeduplicationIdthat is the same as the one generated for the firstMessageDeduplicationId, the two messages are treated as duplicates and only one copy of the message is delivered.
The MessageDeduplicationId is available to the consumer of the message (this can be useful for troubleshooting delivery issues).
If a message is sent successfully but the acknowledgement is lost and the message is resent with the same MessageDeduplicationId after the deduplication interval, Amazon SNS can't detect duplicate messages.
Amazon SNS continues to keep track of the message deduplication ID even after the message is received and deleted.
The length of MessageDeduplicationId is 128 characters.
MessageDeduplicationId can contain alphanumeric characters (a-z, A-Z, 0-9) and punctuation (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~).
sourcepub fn message_group_id(self, input: impl Into<String>) -> Self
pub fn message_group_id(self, input: impl Into<String>) -> Self
This parameter applies only to FIFO (first-in-first-out) topics.
The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message group are processed in a FIFO manner (however, messages in different message groups might be processed out of order). To interleave multiple ordered streams within a single topic, use MessageGroupId values (for example, session data for multiple users). In this scenario, multiple consumers can process the topic, but the session data of each user is processed in a FIFO fashion.
You must associate a non-empty MessageGroupId with a message. If you don't provide a MessageGroupId, the action fails.
The length of MessageGroupId is 128 characters.
MessageGroupId can contain alphanumeric characters (a-z, A-Z, 0-9) and punctuation (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~).
MessageGroupId is required for FIFO topics. You can't use it for standard topics.
sourcepub fn set_message_group_id(self, input: Option<String>) -> Self
pub fn set_message_group_id(self, input: Option<String>) -> Self
This parameter applies only to FIFO (first-in-first-out) topics.
The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message group are processed in a FIFO manner (however, messages in different message groups might be processed out of order). To interleave multiple ordered streams within a single topic, use MessageGroupId values (for example, session data for multiple users). In this scenario, multiple consumers can process the topic, but the session data of each user is processed in a FIFO fashion.
You must associate a non-empty MessageGroupId with a message. If you don't provide a MessageGroupId, the action fails.
The length of MessageGroupId is 128 characters.
MessageGroupId can contain alphanumeric characters (a-z, A-Z, 0-9) and punctuation (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~).
MessageGroupId is required for FIFO topics. You can't use it for standard topics.
sourcepub fn get_message_group_id(&self) -> &Option<String>
pub fn get_message_group_id(&self) -> &Option<String>
This parameter applies only to FIFO (first-in-first-out) topics.
The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message group are processed in a FIFO manner (however, messages in different message groups might be processed out of order). To interleave multiple ordered streams within a single topic, use MessageGroupId values (for example, session data for multiple users). In this scenario, multiple consumers can process the topic, but the session data of each user is processed in a FIFO fashion.
You must associate a non-empty MessageGroupId with a message. If you don't provide a MessageGroupId, the action fails.
The length of MessageGroupId is 128 characters.
MessageGroupId can contain alphanumeric characters (a-z, A-Z, 0-9) and punctuation (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~).
MessageGroupId is required for FIFO topics. You can't use it for standard topics.
sourcepub fn build(self) -> Result<PublishBatchRequestEntry, BuildError>
pub fn build(self) -> Result<PublishBatchRequestEntry, BuildError>
Consumes the builder and constructs a PublishBatchRequestEntry.
This method will fail if any of the following fields are not set:
Trait Implementations§
source§impl Clone for PublishBatchRequestEntryBuilder
impl Clone for PublishBatchRequestEntryBuilder
source§fn clone(&self) -> PublishBatchRequestEntryBuilder
fn clone(&self) -> PublishBatchRequestEntryBuilder
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moresource§impl Default for PublishBatchRequestEntryBuilder
impl Default for PublishBatchRequestEntryBuilder
source§fn default() -> PublishBatchRequestEntryBuilder
fn default() -> PublishBatchRequestEntryBuilder
source§impl PartialEq for PublishBatchRequestEntryBuilder
impl PartialEq for PublishBatchRequestEntryBuilder
source§fn eq(&self, other: &PublishBatchRequestEntryBuilder) -> bool
fn eq(&self, other: &PublishBatchRequestEntryBuilder) -> bool
self and other values to be equal, and is used
by ==.