Struct UpdateContainerServiceInput

#[non_exhaustive]
pub struct UpdateContainerServiceInput {
    pub service_name: Option<String>,
    pub power: Option<ContainerServicePowerName>,
    pub scale: Option<i32>,
    pub is_disabled: Option<bool>,
    pub public_domain_names: Option<HashMap<String, Vec<String>>>,
    pub private_registry_access: Option<PrivateRegistryAccessRequest>,
}

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.

service_name: Option<String>

The name of the container service to update.

power: Option<ContainerServicePowerName>

The power for the container service.

The power specifies the amount of memory, vCPUs, and base monthly cost of each node of the container service. The power and scale of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power with the scale (the number of nodes) of the service.

Use the GetContainerServicePowers action to view the specifications of each power option.

scale: Option<i32>

The scale for the container service.

The scale specifies the allocated compute nodes of the container service. The power and scale of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power with the scale (the number of nodes) of the service.

is_disabled: Option<bool>

A Boolean value to indicate whether the container service is disabled.

public_domain_names: Option<HashMap<String, Vec<String>>>

The public domain names to use with the container service, such as example.com and www.example.com.

You can specify up to four public domain names for a container service. The domain names that you specify are used when you create a deployment with a container configured as the public endpoint of your container service.

If you don't specify public domain names, then you can use the default domain of the container service.

You must create and validate an SSL/TLS certificate before you can use public domain names with your container service. Use the CreateCertificate action to create a certificate for the public domain names you want to use with your container service.

You can specify public domain names using a string to array map as shown in the example later on this page.

private_registry_access: Option<PrivateRegistryAccessRequest>

An object to describe the configuration for the container service to access private container image repositories, such as Amazon Elastic Container Registry (Amazon ECR) private repositories.

For more information, see Configuring access to an Amazon ECR private repository for an Amazon Lightsail container service in the Amazon Lightsail Developer Guide.

Implementations

impl UpdateContainerServiceInput

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

The name of the container service to update.

pub fn power(&self) -> Option<&ContainerServicePowerName>

The power for the container service.

The power specifies the amount of memory, vCPUs, and base monthly cost of each node of the container service. The power and scale of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power with the scale (the number of nodes) of the service.

Use the GetContainerServicePowers action to view the specifications of each power option.

pub fn scale(&self) -> Option<i32>

The scale for the container service.

The scale specifies the allocated compute nodes of the container service. The power and scale of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power with the scale (the number of nodes) of the service.

pub fn is_disabled(&self) -> Option<bool>

A Boolean value to indicate whether the container service is disabled.

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

The public domain names to use with the container service, such as example.com and www.example.com.

You can specify up to four public domain names for a container service. The domain names that you specify are used when you create a deployment with a container configured as the public endpoint of your container service.

If you don't specify public domain names, then you can use the default domain of the container service.

You must create and validate an SSL/TLS certificate before you can use public domain names with your container service. Use the CreateCertificate action to create a certificate for the public domain names you want to use with your container service.

You can specify public domain names using a string to array map as shown in the example later on this page.

pub fn private_registry_access(&self) -> Option<&PrivateRegistryAccessRequest>

An object to describe the configuration for the container service to access private container image repositories, such as Amazon Elastic Container Registry (Amazon ECR) private repositories.

For more information, see Configuring access to an Amazon ECR private repository for an Amazon Lightsail container service in the Amazon Lightsail Developer Guide.

impl UpdateContainerServiceInput

pub fn builder() -> UpdateContainerServiceInputBuilder

Creates a new builder-style object to manufacture UpdateContainerServiceInput.

Trait Implementations

impl Clone for UpdateContainerServiceInput

fn clone(&self) -> UpdateContainerServiceInput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for UpdateContainerServiceInput

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

Formats the value using the given formatter.

impl PartialEq for UpdateContainerServiceInput

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

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

const 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 UpdateContainerServiceInput