Struct CreateStateTemplateInput 

#[non_exhaustive]
pub struct CreateStateTemplateInput {
    pub name: Option<String>,
    pub description: Option<String>,
    pub signal_catalog_arn: Option<String>,
    pub state_template_properties: Option<Vec<String>>,
    pub data_extra_dimensions: Option<Vec<String>>,
    pub metadata_extra_dimensions: Option<Vec<String>>,
    pub tags: Option<Vec<Tag>>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

name: Option<String>

The name of the state template.

description: Option<String>

A brief description of the state template.

signal_catalog_arn: Option<String>

The ARN of the signal catalog associated with the state template.

state_template_properties: Option<Vec<String>>

A list of signals from which data is collected. The state template properties contain the fully qualified names of the signals.

data_extra_dimensions: Option<Vec<String>>

A list of vehicle attributes to associate with the payload published on the state template's MQTT topic. (See Processing last known state vehicle data using MQTT messaging). For example, if you add Vehicle.Attributes.Make and Vehicle.Attributes.Model attributes, Amazon Web Services IoT FleetWise will enrich the protobuf encoded payload with those attributes in the extraDimensions field.

metadata_extra_dimensions: Option<Vec<String>>

A list of vehicle attributes to associate with user properties of the messages published on the state template's MQTT topic. (See Processing last known state vehicle data using MQTT messaging). For example, if you add Vehicle.Attributes.Make and Vehicle.Attributes.Model attributes, Amazon Web Services IoT FleetWise will include these attributes as User Properties with the MQTT message.

Default: An empty array

tags: Option<Vec<Tag>>

Metadata that can be used to manage the state template.

Implementations

impl CreateStateTemplateInput

pub fn name(&self) -> Option<&str>

The name of the state template.

pub fn description(&self) -> Option<&str>

A brief description of the state template.

pub fn signal_catalog_arn(&self) -> Option<&str>

The ARN of the signal catalog associated with the state template.

pub fn state_template_properties(&self) -> &[String]

A list of signals from which data is collected. The state template properties contain the fully qualified names of the signals.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .state_template_properties.is_none().

pub fn data_extra_dimensions(&self) -> &[String]

A list of vehicle attributes to associate with the payload published on the state template's MQTT topic. (See Processing last known state vehicle data using MQTT messaging). For example, if you add Vehicle.Attributes.Make and Vehicle.Attributes.Model attributes, Amazon Web Services IoT FleetWise will enrich the protobuf encoded payload with those attributes in the extraDimensions field.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .data_extra_dimensions.is_none().

pub fn metadata_extra_dimensions(&self) -> &[String]

A list of vehicle attributes to associate with user properties of the messages published on the state template's MQTT topic. (See Processing last known state vehicle data using MQTT messaging). For example, if you add Vehicle.Attributes.Make and Vehicle.Attributes.Model attributes, Amazon Web Services IoT FleetWise will include these attributes as User Properties with the MQTT message.

Default: An empty array

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .metadata_extra_dimensions.is_none().

pub fn tags(&self) -> &[Tag]

Metadata that can be used to manage the state template.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .tags.is_none().

impl CreateStateTemplateInput

pub fn builder() -> CreateStateTemplateInputBuilder

Creates a new builder-style object to manufacture CreateStateTemplateInput.

Trait Implementations

impl Clone for CreateStateTemplateInput

fn clone(&self) -> CreateStateTemplateInput

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreateStateTemplateInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for CreateStateTemplateInput

fn eq(&self, other: &CreateStateTemplateInput) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for CreateStateTemplateInput