pub struct CreateContainerServiceFluentBuilder { /* private fields */ }
Expand description
Fluent builder constructing a request to CreateContainerService
.
Creates an Amazon Lightsail container service.
A Lightsail container service is a compute resource to which you can deploy containers. For more information, see Container services in Amazon Lightsail in the Lightsail Dev Guide.
Implementations§
Source§impl CreateContainerServiceFluentBuilder
impl CreateContainerServiceFluentBuilder
Sourcepub fn as_input(&self) -> &CreateContainerServiceInputBuilder
pub fn as_input(&self) -> &CreateContainerServiceInputBuilder
Access the CreateContainerService as a reference.
Sourcepub async fn send(
self,
) -> Result<CreateContainerServiceOutput, SdkError<CreateContainerServiceError, HttpResponse>>
pub async fn send( self, ) -> Result<CreateContainerServiceOutput, SdkError<CreateContainerServiceError, HttpResponse>>
Sends the request and returns the response.
If an error occurs, an SdkError
will be returned with additional details that
can be matched against.
By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.
Sourcepub fn customize(
self,
) -> CustomizableOperation<CreateContainerServiceOutput, CreateContainerServiceError, Self>
pub fn customize( self, ) -> CustomizableOperation<CreateContainerServiceOutput, CreateContainerServiceError, Self>
Consumes this builder, creating a customizable operation that can be modified before being sent.
Sourcepub fn service_name(self, input: impl Into<String>) -> Self
pub fn service_name(self, input: impl Into<String>) -> Self
The name for the container service.
The name that you specify for your container service will make up part of its default domain. The default domain of a container service is typically https://
. If the name of your container service is container-service-1
, and it's located in the US East (Ohio) Amazon Web Services Region (us-east-2
), then the domain for your container service will be like the following example: https://container-service-1.ur4EXAMPLE2uq.us-east-2.cs.amazonlightsail.com
The following are the requirements for container service names:
-
Must be unique within each Amazon Web Services Region in your Lightsail account.
-
Must contain 1 to 63 characters.
-
Must contain only alphanumeric characters and hyphens.
-
A hyphen (-) can separate words but cannot be at the start or end of the name.
Sourcepub fn set_service_name(self, input: Option<String>) -> Self
pub fn set_service_name(self, input: Option<String>) -> Self
The name for the container service.
The name that you specify for your container service will make up part of its default domain. The default domain of a container service is typically https://
. If the name of your container service is container-service-1
, and it's located in the US East (Ohio) Amazon Web Services Region (us-east-2
), then the domain for your container service will be like the following example: https://container-service-1.ur4EXAMPLE2uq.us-east-2.cs.amazonlightsail.com
The following are the requirements for container service names:
-
Must be unique within each Amazon Web Services Region in your Lightsail account.
-
Must contain 1 to 63 characters.
-
Must contain only alphanumeric characters and hyphens.
-
A hyphen (-) can separate words but cannot be at the start or end of the name.
Sourcepub fn get_service_name(&self) -> &Option<String>
pub fn get_service_name(&self) -> &Option<String>
The name for the container service.
The name that you specify for your container service will make up part of its default domain. The default domain of a container service is typically https://
. If the name of your container service is container-service-1
, and it's located in the US East (Ohio) Amazon Web Services Region (us-east-2
), then the domain for your container service will be like the following example: https://container-service-1.ur4EXAMPLE2uq.us-east-2.cs.amazonlightsail.com
The following are the requirements for container service names:
-
Must be unique within each Amazon Web Services Region in your Lightsail account.
-
Must contain 1 to 63 characters.
-
Must contain only alphanumeric characters and hyphens.
-
A hyphen (-) can separate words but cannot be at the start or end of the name.
Sourcepub fn power(self, input: ContainerServicePowerName) -> Self
pub fn power(self, input: ContainerServicePowerName) -> Self
The power specification 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 get a list of power options that you can specify using this parameter, and their base monthly cost.
Sourcepub fn set_power(self, input: Option<ContainerServicePowerName>) -> Self
pub fn set_power(self, input: Option<ContainerServicePowerName>) -> Self
The power specification 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 get a list of power options that you can specify using this parameter, and their base monthly cost.
Sourcepub fn get_power(&self) -> &Option<ContainerServicePowerName>
pub fn get_power(&self) -> &Option<ContainerServicePowerName>
The power specification 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 get a list of power options that you can specify using this parameter, and their base monthly cost.
Sourcepub fn scale(self, input: i32) -> Self
pub fn scale(self, input: i32) -> Self
The scale specification 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.
Sourcepub fn set_scale(self, input: Option<i32>) -> Self
pub fn set_scale(self, input: Option<i32>) -> Self
The scale specification 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.
Sourcepub fn get_scale(&self) -> &Option<i32>
pub fn get_scale(&self) -> &Option<i32>
The scale specification 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.
Appends an item to tags
.
To override the contents of this collection use set_tags
.
The tag keys and optional values to add to the container service during create.
Use the TagResource
action to tag a resource after it's created.
For more information about tags in Lightsail, see the Amazon Lightsail Developer Guide.
The tag keys and optional values to add to the container service during create.
Use the TagResource
action to tag a resource after it's created.
For more information about tags in Lightsail, see the Amazon Lightsail Developer Guide.
The tag keys and optional values to add to the container service during create.
Use the TagResource
action to tag a resource after it's created.
For more information about tags in Lightsail, see the Amazon Lightsail Developer Guide.
Sourcepub fn public_domain_names(self, k: impl Into<String>, v: Vec<String>) -> Self
pub fn public_domain_names(self, k: impl Into<String>, v: Vec<String>) -> Self
Adds a key-value pair to publicDomainNames
.
To override the contents of this collection use set_public_domain_names
.
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.
Sourcepub fn set_public_domain_names(
self,
input: Option<HashMap<String, Vec<String>>>,
) -> Self
pub fn set_public_domain_names( self, input: Option<HashMap<String, Vec<String>>>, ) -> Self
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.
Sourcepub fn get_public_domain_names(&self) -> &Option<HashMap<String, Vec<String>>>
pub fn get_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.
Sourcepub fn deployment(self, input: ContainerServiceDeploymentRequest) -> Self
pub fn deployment(self, input: ContainerServiceDeploymentRequest) -> Self
An object that describes a deployment for the container service.
A deployment specifies the containers that will be launched on the container service and their settings, such as the ports to open, the environment variables to apply, and the launch command to run. It also specifies the container that will serve as the public endpoint of the deployment and its settings, such as the HTTP or HTTPS port to use, and the health check configuration.
Sourcepub fn set_deployment(
self,
input: Option<ContainerServiceDeploymentRequest>,
) -> Self
pub fn set_deployment( self, input: Option<ContainerServiceDeploymentRequest>, ) -> Self
An object that describes a deployment for the container service.
A deployment specifies the containers that will be launched on the container service and their settings, such as the ports to open, the environment variables to apply, and the launch command to run. It also specifies the container that will serve as the public endpoint of the deployment and its settings, such as the HTTP or HTTPS port to use, and the health check configuration.
Sourcepub fn get_deployment(&self) -> &Option<ContainerServiceDeploymentRequest>
pub fn get_deployment(&self) -> &Option<ContainerServiceDeploymentRequest>
An object that describes a deployment for the container service.
A deployment specifies the containers that will be launched on the container service and their settings, such as the ports to open, the environment variables to apply, and the launch command to run. It also specifies the container that will serve as the public endpoint of the deployment and its settings, such as the HTTP or HTTPS port to use, and the health check configuration.
Sourcepub fn private_registry_access(
self,
input: PrivateRegistryAccessRequest,
) -> Self
pub fn private_registry_access( self, input: PrivateRegistryAccessRequest, ) -> Self
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.
Sourcepub fn set_private_registry_access(
self,
input: Option<PrivateRegistryAccessRequest>,
) -> Self
pub fn set_private_registry_access( self, input: Option<PrivateRegistryAccessRequest>, ) -> Self
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.
Sourcepub fn get_private_registry_access(
&self,
) -> &Option<PrivateRegistryAccessRequest>
pub fn get_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.
Trait Implementations§
Source§impl Clone for CreateContainerServiceFluentBuilder
impl Clone for CreateContainerServiceFluentBuilder
Source§fn clone(&self) -> CreateContainerServiceFluentBuilder
fn clone(&self) -> CreateContainerServiceFluentBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreAuto Trait Implementations§
impl Freeze for CreateContainerServiceFluentBuilder
impl !RefUnwindSafe for CreateContainerServiceFluentBuilder
impl Send for CreateContainerServiceFluentBuilder
impl Sync for CreateContainerServiceFluentBuilder
impl Unpin for CreateContainerServiceFluentBuilder
impl !UnwindSafe for CreateContainerServiceFluentBuilder
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);