#[non_exhaustive]pub struct ContainerOverrides {
pub vcpus: Option<i32>,
pub memory: Option<i32>,
pub command: Option<Vec<String>>,
pub instance_type: Option<String>,
pub environment: Option<Vec<KeyValuePair>>,
pub resource_requirements: Option<Vec<ResourceRequirement>>,
}
Expand description
The overrides that should be sent to a container.
For information about using Batch overrides when you connect event sources to targets, see BatchContainerOverrides.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.vcpus: Option<i32>
This parameter is deprecated, use resourceRequirements
to override the vcpus
parameter that's set in the job definition. It's not supported for jobs running on Fargate resources. For jobs that run on Amazon EC2 resources, it overrides the vcpus
parameter set in the job definition, but doesn't override any vCPU requirement specified in the resourceRequirements
structure in the job definition. To override vCPU requirements that are specified in the resourceRequirements
structure in the job definition, resourceRequirements
must be specified in the SubmitJob
request, with type
set to VCPU
and value
set to the new value. For more information, see Can't override job definition resource requirements in the Batch User Guide.
memory: Option<i32>
This parameter is deprecated, use resourceRequirements
to override the memory requirements specified in the job definition. It's not supported for jobs running on Fargate resources. For jobs that run on Amazon EC2 resources, it overrides the memory
parameter set in the job definition, but doesn't override any memory requirement that's specified in the resourceRequirements
structure in the job definition. To override memory requirements that are specified in the resourceRequirements
structure in the job definition, resourceRequirements
must be specified in the SubmitJob
request, with type
set to MEMORY
and value
set to the new value. For more information, see Can't override job definition resource requirements in the Batch User Guide.
command: Option<Vec<String>>
The command to send to the container that overrides the default command from the Docker image or the job definition.
This parameter can't contain an empty string.
instance_type: Option<String>
The instance type to use for a multi-node parallel job.
This parameter isn't applicable to single-node container jobs or jobs that run on Fargate resources, and shouldn't be provided.
environment: Option<Vec<KeyValuePair>>
The environment variables to send to the container. You can add new environment variables, which are added to the container at launch, or you can override the existing environment variables from the Docker image or the job definition.
Environment variables cannot start with "AWS_BATCH
". This naming convention is reserved for variables that Batch sets.
resource_requirements: Option<Vec<ResourceRequirement>>
The type and amount of resources to assign to a container. This overrides the settings in the job definition. The supported resources include GPU
, MEMORY
, and VCPU
.
Implementations§
Source§impl ContainerOverrides
impl ContainerOverrides
Sourcepub fn vcpus(&self) -> Option<i32>
👎Deprecated: This field is deprecated, use resourceRequirements instead.
pub fn vcpus(&self) -> Option<i32>
This parameter is deprecated, use resourceRequirements
to override the vcpus
parameter that's set in the job definition. It's not supported for jobs running on Fargate resources. For jobs that run on Amazon EC2 resources, it overrides the vcpus
parameter set in the job definition, but doesn't override any vCPU requirement specified in the resourceRequirements
structure in the job definition. To override vCPU requirements that are specified in the resourceRequirements
structure in the job definition, resourceRequirements
must be specified in the SubmitJob
request, with type
set to VCPU
and value
set to the new value. For more information, see Can't override job definition resource requirements in the Batch User Guide.
Sourcepub fn memory(&self) -> Option<i32>
👎Deprecated: This field is deprecated, use resourceRequirements instead.
pub fn memory(&self) -> Option<i32>
This parameter is deprecated, use resourceRequirements
to override the memory requirements specified in the job definition. It's not supported for jobs running on Fargate resources. For jobs that run on Amazon EC2 resources, it overrides the memory
parameter set in the job definition, but doesn't override any memory requirement that's specified in the resourceRequirements
structure in the job definition. To override memory requirements that are specified in the resourceRequirements
structure in the job definition, resourceRequirements
must be specified in the SubmitJob
request, with type
set to MEMORY
and value
set to the new value. For more information, see Can't override job definition resource requirements in the Batch User Guide.
Sourcepub fn command(&self) -> &[String]
pub fn command(&self) -> &[String]
The command to send to the container that overrides the default command from the Docker image or the job definition.
This parameter can't contain an empty string.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .command.is_none()
.
Sourcepub fn instance_type(&self) -> Option<&str>
pub fn instance_type(&self) -> Option<&str>
The instance type to use for a multi-node parallel job.
This parameter isn't applicable to single-node container jobs or jobs that run on Fargate resources, and shouldn't be provided.
Sourcepub fn environment(&self) -> &[KeyValuePair]
pub fn environment(&self) -> &[KeyValuePair]
The environment variables to send to the container. You can add new environment variables, which are added to the container at launch, or you can override the existing environment variables from the Docker image or the job definition.
Environment variables cannot start with "AWS_BATCH
". This naming convention is reserved for variables that Batch sets.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .environment.is_none()
.
Sourcepub fn resource_requirements(&self) -> &[ResourceRequirement]
pub fn resource_requirements(&self) -> &[ResourceRequirement]
The type and amount of resources to assign to a container. This overrides the settings in the job definition. The supported resources include GPU
, MEMORY
, and VCPU
.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .resource_requirements.is_none()
.
Source§impl ContainerOverrides
impl ContainerOverrides
Sourcepub fn builder() -> ContainerOverridesBuilder
pub fn builder() -> ContainerOverridesBuilder
Creates a new builder-style object to manufacture ContainerOverrides
.
Trait Implementations§
Source§impl Clone for ContainerOverrides
impl Clone for ContainerOverrides
Source§fn clone(&self) -> ContainerOverrides
fn clone(&self) -> ContainerOverrides
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for ContainerOverrides
impl Debug for ContainerOverrides
Source§impl PartialEq for ContainerOverrides
impl PartialEq for ContainerOverrides
impl StructuralPartialEq for ContainerOverrides
Auto Trait Implementations§
impl Freeze for ContainerOverrides
impl RefUnwindSafe for ContainerOverrides
impl Send for ContainerOverrides
impl Sync for ContainerOverrides
impl Unpin for ContainerOverrides
impl UnwindSafe for ContainerOverrides
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);