#[non_exhaustive]pub struct LaunchTemplateSpecificationBuilder { /* private fields */ }
Expand description
A builder for LaunchTemplateSpecification
.
Implementations§
Source§impl LaunchTemplateSpecificationBuilder
impl LaunchTemplateSpecificationBuilder
Sourcepub fn launch_template_id(self, input: impl Into<String>) -> Self
pub fn launch_template_id(self, input: impl Into<String>) -> Self
The ID of the launch template.
Sourcepub fn set_launch_template_id(self, input: Option<String>) -> Self
pub fn set_launch_template_id(self, input: Option<String>) -> Self
The ID of the launch template.
Sourcepub fn get_launch_template_id(&self) -> &Option<String>
pub fn get_launch_template_id(&self) -> &Option<String>
The ID of the launch template.
Sourcepub fn launch_template_name(self, input: impl Into<String>) -> Self
pub fn launch_template_name(self, input: impl Into<String>) -> Self
The name of the launch template.
Sourcepub fn set_launch_template_name(self, input: Option<String>) -> Self
pub fn set_launch_template_name(self, input: Option<String>) -> Self
The name of the launch template.
Sourcepub fn get_launch_template_name(&self) -> &Option<String>
pub fn get_launch_template_name(&self) -> &Option<String>
The name of the launch template.
Sourcepub fn version(self, input: impl Into<String>) -> Self
pub fn version(self, input: impl Into<String>) -> Self
The version number of the launch template, $Default
, or $Latest
.
If the value is $Default
, the default version of the launch template is used. If the value is $Latest
, the latest version of the launch template is used.
If the AMI ID that's used in a compute environment is from the launch template, the AMI isn't changed when the compute environment is updated. It's only changed if the updateToLatestImageVersion
parameter for the compute environment is set to true
. During an infrastructure update, if either $Default
or $Latest
is specified, Batch re-evaluates the launch template version, and it might use a different version of the launch template. This is the case even if the launch template isn't specified in the update. When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
Default: $Default
Latest: $Latest
Sourcepub fn set_version(self, input: Option<String>) -> Self
pub fn set_version(self, input: Option<String>) -> Self
The version number of the launch template, $Default
, or $Latest
.
If the value is $Default
, the default version of the launch template is used. If the value is $Latest
, the latest version of the launch template is used.
If the AMI ID that's used in a compute environment is from the launch template, the AMI isn't changed when the compute environment is updated. It's only changed if the updateToLatestImageVersion
parameter for the compute environment is set to true
. During an infrastructure update, if either $Default
or $Latest
is specified, Batch re-evaluates the launch template version, and it might use a different version of the launch template. This is the case even if the launch template isn't specified in the update. When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
Default: $Default
Latest: $Latest
Sourcepub fn get_version(&self) -> &Option<String>
pub fn get_version(&self) -> &Option<String>
The version number of the launch template, $Default
, or $Latest
.
If the value is $Default
, the default version of the launch template is used. If the value is $Latest
, the latest version of the launch template is used.
If the AMI ID that's used in a compute environment is from the launch template, the AMI isn't changed when the compute environment is updated. It's only changed if the updateToLatestImageVersion
parameter for the compute environment is set to true
. During an infrastructure update, if either $Default
or $Latest
is specified, Batch re-evaluates the launch template version, and it might use a different version of the launch template. This is the case even if the launch template isn't specified in the update. When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
Default: $Default
Latest: $Latest
Sourcepub fn overrides(self, input: LaunchTemplateSpecificationOverride) -> Self
pub fn overrides(self, input: LaunchTemplateSpecificationOverride) -> Self
Appends an item to overrides
.
To override the contents of this collection use set_overrides
.
A launch template to use in place of the default launch template. You must specify either the launch template ID or launch template name in the request, but not both.
You can specify up to ten (10) launch template overrides that are associated to unique instance types or families for each compute environment.
To unset all override templates for a compute environment, you can pass an empty array to the UpdateComputeEnvironment.overrides parameter, or not include the overrides
parameter when submitting the UpdateComputeEnvironment
API operation.
Sourcepub fn set_overrides(
self,
input: Option<Vec<LaunchTemplateSpecificationOverride>>,
) -> Self
pub fn set_overrides( self, input: Option<Vec<LaunchTemplateSpecificationOverride>>, ) -> Self
A launch template to use in place of the default launch template. You must specify either the launch template ID or launch template name in the request, but not both.
You can specify up to ten (10) launch template overrides that are associated to unique instance types or families for each compute environment.
To unset all override templates for a compute environment, you can pass an empty array to the UpdateComputeEnvironment.overrides parameter, or not include the overrides
parameter when submitting the UpdateComputeEnvironment
API operation.
Sourcepub fn get_overrides(&self) -> &Option<Vec<LaunchTemplateSpecificationOverride>>
pub fn get_overrides(&self) -> &Option<Vec<LaunchTemplateSpecificationOverride>>
A launch template to use in place of the default launch template. You must specify either the launch template ID or launch template name in the request, but not both.
You can specify up to ten (10) launch template overrides that are associated to unique instance types or families for each compute environment.
To unset all override templates for a compute environment, you can pass an empty array to the UpdateComputeEnvironment.overrides parameter, or not include the overrides
parameter when submitting the UpdateComputeEnvironment
API operation.
Sourcepub fn userdata_type(self, input: UserdataType) -> Self
pub fn userdata_type(self, input: UserdataType) -> Self
The EKS node initialization process to use. You only need to specify this value if you are using a custom AMI. The default value is EKS_BOOTSTRAP_SH
. If imageType is a custom AMI based on EKS_AL2023 or EKS_AL2023_NVIDIA then you must choose EKS_NODEADM
.
Sourcepub fn set_userdata_type(self, input: Option<UserdataType>) -> Self
pub fn set_userdata_type(self, input: Option<UserdataType>) -> Self
The EKS node initialization process to use. You only need to specify this value if you are using a custom AMI. The default value is EKS_BOOTSTRAP_SH
. If imageType is a custom AMI based on EKS_AL2023 or EKS_AL2023_NVIDIA then you must choose EKS_NODEADM
.
Sourcepub fn get_userdata_type(&self) -> &Option<UserdataType>
pub fn get_userdata_type(&self) -> &Option<UserdataType>
The EKS node initialization process to use. You only need to specify this value if you are using a custom AMI. The default value is EKS_BOOTSTRAP_SH
. If imageType is a custom AMI based on EKS_AL2023 or EKS_AL2023_NVIDIA then you must choose EKS_NODEADM
.
Sourcepub fn build(self) -> LaunchTemplateSpecification
pub fn build(self) -> LaunchTemplateSpecification
Consumes the builder and constructs a LaunchTemplateSpecification
.
Trait Implementations§
Source§impl Clone for LaunchTemplateSpecificationBuilder
impl Clone for LaunchTemplateSpecificationBuilder
Source§fn clone(&self) -> LaunchTemplateSpecificationBuilder
fn clone(&self) -> LaunchTemplateSpecificationBuilder
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Default for LaunchTemplateSpecificationBuilder
impl Default for LaunchTemplateSpecificationBuilder
Source§fn default() -> LaunchTemplateSpecificationBuilder
fn default() -> LaunchTemplateSpecificationBuilder
Source§impl PartialEq for LaunchTemplateSpecificationBuilder
impl PartialEq for LaunchTemplateSpecificationBuilder
Source§fn eq(&self, other: &LaunchTemplateSpecificationBuilder) -> bool
fn eq(&self, other: &LaunchTemplateSpecificationBuilder) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for LaunchTemplateSpecificationBuilder
Auto Trait Implementations§
impl Freeze for LaunchTemplateSpecificationBuilder
impl RefUnwindSafe for LaunchTemplateSpecificationBuilder
impl Send for LaunchTemplateSpecificationBuilder
impl Sync for LaunchTemplateSpecificationBuilder
impl Unpin for LaunchTemplateSpecificationBuilder
impl UnwindSafe for LaunchTemplateSpecificationBuilder
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);