Struct CreateContainerRecipeInput

#[non_exhaustive]
pub struct CreateContainerRecipeInput {

    pub container_type: Option<ContainerType>,
    pub name: Option<String>,
    pub description: Option<String>,
    pub semantic_version: Option<String>,
    pub components: Option<Vec<ComponentConfiguration>>,
    pub instance_configuration: Option<InstanceConfiguration>,
    pub dockerfile_template_data: Option<String>,
    pub dockerfile_template_uri: Option<String>,
    pub platform_override: Option<Platform>,
    pub image_os_version_override: Option<String>,
    pub parent_image: Option<String>,
    pub tags: Option<HashMap<String, String>>,
    pub working_directory: Option<String>,
    pub target_repository: Option<TargetContainerRepository>,
    pub kms_key_id: Option<String>,
    pub client_token: Option<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.

container_type: Option<ContainerType>

The type of container to create.

name: Option<String>

The name of the container recipe.

description: Option<String>

The description of the container recipe.

semantic_version: Option<String>

The semantic version of the container recipe. This version follows the semantic version syntax.

The semantic version has four nodes: . . / . You can assign values for the first three, and can filter on all of them.

Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.

Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.

components: Option<Vec<ComponentConfiguration>>

Components for build and test that are included in the container recipe. Recipes require a minimum of one build component, and can have a maximum of 20 build and test components in any combination.

instance_configuration: Option<InstanceConfiguration>

A group of options that can be used to configure an instance for building and testing container images.

dockerfile_template_data: Option<String>

The Dockerfile template used to build your image as an inline data blob.

dockerfile_template_uri: Option<String>

The Amazon S3 URI for the Dockerfile that will be used to build your container image.

platform_override: Option<Platform>

Specifies the operating system platform when you use a custom base image.

image_os_version_override: Option<String>

Specifies the operating system version for the base image.

parent_image: Option<String>

The base image for the container recipe.

tags: Option<HashMap<String, String>>

Tags that are attached to the container recipe.

working_directory: Option<String>

The working directory for use during build and test workflows.

target_repository: Option<TargetContainerRepository>

The destination repository for the container image.

kms_key_id: Option<String>

Identifies which KMS key is used to encrypt the Dockerfile template.

client_token: Option<String>

Unique, case-sensitive identifier you provide to ensure idempotency of the request. For more information, see Ensuring idempotency in the Amazon EC2 API Reference.

Implementations

impl CreateContainerRecipeInput

pub fn container_type(&self) -> Option<&ContainerType>

The type of container to create.

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

The name of the container recipe.

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

The description of the container recipe.

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

The semantic version of the container recipe. This version follows the semantic version syntax.

The semantic version has four nodes: . . / . You can assign values for the first three, and can filter on all of them.

Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.

Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.

pub fn components(&self) -> &[ComponentConfiguration]

Components for build and test that are included in the container recipe. Recipes require a minimum of one build component, and can have a maximum of 20 build and test components in any combination.

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

pub fn instance_configuration(&self) -> Option<&InstanceConfiguration>

A group of options that can be used to configure an instance for building and testing container images.

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

The Dockerfile template used to build your image as an inline data blob.

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

The Amazon S3 URI for the Dockerfile that will be used to build your container image.

pub fn platform_override(&self) -> Option<&Platform>

Specifies the operating system platform when you use a custom base image.

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

Specifies the operating system version for the base image.

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

The base image for the container recipe.

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

Tags that are attached to the container recipe.

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

The working directory for use during build and test workflows.

pub fn target_repository(&self) -> Option<&TargetContainerRepository>

The destination repository for the container image.

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

Identifies which KMS key is used to encrypt the Dockerfile template.

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

Unique, case-sensitive identifier you provide to ensure idempotency of the request. For more information, see Ensuring idempotency in the Amazon EC2 API Reference.

impl CreateContainerRecipeInput

pub fn builder() -> CreateContainerRecipeInputBuilder

Creates a new builder-style object to manufacture CreateContainerRecipeInput.

Trait Implementations

impl Clone for CreateContainerRecipeInput

fn clone(&self) -> CreateContainerRecipeInput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for CreateContainerRecipeInput

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

Formats the value using the given formatter.

impl PartialEq for CreateContainerRecipeInput

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