Struct CreateLaunchInput 

#[non_exhaustive]
pub struct CreateLaunchInput {
    pub project: Option<String>,
    pub name: Option<String>,
    pub description: Option<String>,
    pub scheduled_splits_config: Option<ScheduledSplitsLaunchConfig>,
    pub metric_monitors: Option<Vec<MetricMonitorConfig>>,
    pub groups: Option<Vec<LaunchGroupConfig>>,
    pub randomization_salt: Option<String>,
    pub tags: Option<HashMap<String, String>>,
}

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.

project: Option<String>

The name or ARN of the project that you want to create the launch in.

name: Option<String>

The name for the new launch.

description: Option<String>

An optional description for the launch.

scheduled_splits_config: Option<ScheduledSplitsLaunchConfig>

An array of structures that define the traffic allocation percentages among the feature variations during each step of the launch.

metric_monitors: Option<Vec<MetricMonitorConfig>>

An array of structures that define the metrics that will be used to monitor the launch performance.

groups: Option<Vec<LaunchGroupConfig>>

An array of structures that contains the feature and variations that are to be used for the launch.

randomization_salt: Option<String>

When Evidently assigns a particular user session to a launch, it must use a randomization ID to determine which variation the user session is served. This randomization ID is a combination of the entity ID and randomizationSalt. If you omit randomizationSalt, Evidently uses the launch name as the randomizationSalt.

tags: Option<HashMap<String, String>>

Assigns one or more tags (key-value pairs) to the launch.

Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.

Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.

You can associate as many as 50 tags with a launch.

For more information, see Tagging Amazon Web Services resources.

Implementations

impl CreateLaunchInput

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

The name or ARN of the project that you want to create the launch in.

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

The name for the new launch.

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

An optional description for the launch.

pub fn scheduled_splits_config(&self) -> Option<&ScheduledSplitsLaunchConfig>

An array of structures that define the traffic allocation percentages among the feature variations during each step of the launch.

pub fn metric_monitors(&self) -> &[MetricMonitorConfig]

An array of structures that define the metrics that will be used to monitor the launch performance.

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

pub fn groups(&self) -> &[LaunchGroupConfig]

An array of structures that contains the feature and variations that are to be used for the launch.

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

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

When Evidently assigns a particular user session to a launch, it must use a randomization ID to determine which variation the user session is served. This randomization ID is a combination of the entity ID and randomizationSalt. If you omit randomizationSalt, Evidently uses the launch name as the randomizationSalt.

pub fn tags(&self) -> Option<&HashMap<String, String>>

Assigns one or more tags (key-value pairs) to the launch.

Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.

Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.

You can associate as many as 50 tags with a launch.

For more information, see Tagging Amazon Web Services resources.

impl CreateLaunchInput

pub fn builder() -> CreateLaunchInputBuilder

Creates a new builder-style object to manufacture CreateLaunchInput.

Trait Implementations

impl Clone for CreateLaunchInput

fn clone(&self) -> CreateLaunchInput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for CreateLaunchInput

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

Formats the value using the given formatter.

impl PartialEq for CreateLaunchInput

fn eq(&self, other: &CreateLaunchInput) -> 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 CreateLaunchInput