#[non_exhaustive]pub struct ContainerProperties {Show 24 fields
pub image: Option<String>,
pub vcpus: Option<i32>,
pub memory: Option<i32>,
pub command: Option<Vec<String>>,
pub job_role_arn: Option<String>,
pub execution_role_arn: Option<String>,
pub volumes: Option<Vec<Volume>>,
pub environment: Option<Vec<KeyValuePair>>,
pub mount_points: Option<Vec<MountPoint>>,
pub readonly_root_filesystem: Option<bool>,
pub privileged: Option<bool>,
pub ulimits: Option<Vec<Ulimit>>,
pub user: Option<String>,
pub instance_type: Option<String>,
pub resource_requirements: Option<Vec<ResourceRequirement>>,
pub linux_parameters: Option<LinuxParameters>,
pub log_configuration: Option<LogConfiguration>,
pub secrets: Option<Vec<Secret>>,
pub network_configuration: Option<NetworkConfiguration>,
pub fargate_platform_configuration: Option<FargatePlatformConfiguration>,
pub enable_execute_command: Option<bool>,
pub ephemeral_storage: Option<EphemeralStorage>,
pub runtime_platform: Option<RuntimePlatform>,
pub repository_credentials: Option<RepositoryCredentials>,
}
Expand description
Container properties are used for Amazon ECS based job definitions. These properties to describe the container that's launched as part of a job.
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.image: Option<String>
Required. The image used to start a container. This string is passed directly to the Docker daemon. Images in the Docker Hub registry are available by default. Other repositories are specified with repository-url/image:tag
. It can be 255 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), underscores (_), colons (:), periods (.), forward slashes (/), and number signs (#). This parameter maps to Image
in the Create a container section of the Docker Remote API and the IMAGE
parameter of docker run.
Docker image architecture must match the processor architecture of the compute resources that they're scheduled on. For example, ARM-based Docker images can only run on ARM-based compute resources.
-
Images in Amazon ECR Public repositories use the full
registry/repository\[:tag\]
orregistry/repository\[@digest\]
naming conventions. For example,public.ecr.aws/registry_alias/my-web-app:latest
. -
Images in Amazon ECR repositories use the full registry and repository URI (for example,
123456789012.dkr.ecr.
)..amazonaws.com/ -
Images in official repositories on Docker Hub use a single name (for example,
ubuntu
ormongo
). -
Images in other repositories on Docker Hub are qualified with an organization name (for example,
amazon/amazon-ecs-agent
). -
Images in other online repositories are qualified further by a domain name (for example,
quay.io/assemblyline/ubuntu
).
vcpus: Option<i32>
This parameter is deprecated, use resourceRequirements
to specify the vCPU requirements for the job definition. It's not supported for jobs running on Fargate resources. For jobs running on Amazon EC2 resources, it specifies the number of vCPUs reserved for the job.
Each vCPU is equivalent to 1,024 CPU shares. This parameter maps to CpuShares
in the Create a container section of the Docker Remote API and the --cpu-shares
option to docker run. The number of vCPUs must be specified but can be specified in several places. You must specify it at least once for each node.
memory: Option<i32>
This parameter is deprecated, use resourceRequirements
to specify the memory requirements for the job definition. It's not supported for jobs running on Fargate resources. For jobs that run on Amazon EC2 resources, it specifies the memory hard limit (in MiB) for a container. If your container attempts to exceed the specified number, it's terminated. You must specify at least 4 MiB of memory for a job using this parameter. The memory hard limit can be specified in several places. It must be specified for each node at least once.
command: Option<Vec<String>>
The command that's passed to the container. This parameter maps to Cmd
in the Create a container section of the Docker Remote API and the COMMAND
parameter to docker run. For more information, see https://docs.docker.com/engine/reference/builder/#cmd.
job_role_arn: Option<String>
The Amazon Resource Name (ARN) of the IAM role that the container can assume for Amazon Web Services permissions. For more information, see IAM roles for tasks in the Amazon Elastic Container Service Developer Guide.
execution_role_arn: Option<String>
The Amazon Resource Name (ARN) of the execution role that Batch can assume. For jobs that run on Fargate resources, you must provide an execution role. For more information, see Batch execution IAM role in the Batch User Guide.
volumes: Option<Vec<Volume>>
A list of data volumes used in a job.
environment: Option<Vec<KeyValuePair>>
The environment variables to pass to a container. This parameter maps to Env
in the Create a container section of the Docker Remote API and the --env
option to docker run.
We don't recommend using plaintext environment variables for sensitive information, such as credential data.
Environment variables cannot start with "AWS_BATCH
". This naming convention is reserved for variables that Batch sets.
mount_points: Option<Vec<MountPoint>>
The mount points for data volumes in your container. This parameter maps to Volumes
in the Create a container section of the Docker Remote API and the --volume
option to docker run.
readonly_root_filesystem: Option<bool>
When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs
in the Create a container section of the Docker Remote API and the --read-only
option to docker run
.
privileged: Option<bool>
When this parameter is true, the container is given elevated permissions on the host container instance (similar to the root
user). This parameter maps to Privileged
in the Create a container section of the Docker Remote API and the --privileged
option to docker run. The default value is false.
This parameter isn't applicable to jobs that are running on Fargate resources and shouldn't be provided, or specified as false.
ulimits: Option<Vec<Ulimit>>
A list of ulimits
to set in the container. This parameter maps to Ulimits
in the Create a container section of the Docker Remote API and the --ulimit
option to docker run.
This parameter isn't applicable to jobs that are running on Fargate resources and shouldn't be provided.
user: Option<String>
The user name to use inside the container. This parameter maps to User
in the Create a container section of the Docker Remote API and the --user
option to docker run.
instance_type: Option<String>
The instance type to use for a multi-node parallel job. All node groups in a multi-node parallel job must use the same instance type.
This parameter isn't applicable to single-node container jobs or jobs that run on Fargate resources, and shouldn't be provided.
resource_requirements: Option<Vec<ResourceRequirement>>
The type and amount of resources to assign to a container. The supported resources include GPU
, MEMORY
, and VCPU
.
linux_parameters: Option<LinuxParameters>
Linux-specific modifications that are applied to the container, such as details for device mappings.
log_configuration: Option<LogConfiguration>
The log configuration specification for the container.
This parameter maps to LogConfig
in the Create a container section of the Docker Remote API and the --log-driver
option to docker run. By default, containers use the same logging driver that the Docker daemon uses. However the container might use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance (or on a different log server for remote logging options). For more information on the options for different supported log drivers, see Configure logging drivers in the Docker documentation.
Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type).
This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version | grep "Server API version"
The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS
environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide.
secrets: Option<Vec<Secret>>
The secrets for the container. For more information, see Specifying sensitive data in the Batch User Guide.
network_configuration: Option<NetworkConfiguration>
The network configuration for jobs that are running on Fargate resources. Jobs that are running on Amazon EC2 resources must not specify this parameter.
fargate_platform_configuration: Option<FargatePlatformConfiguration>
The platform configuration for jobs that are running on Fargate resources. Jobs that are running on Amazon EC2 resources must not specify this parameter.
enable_execute_command: Option<bool>
Determines whether execute command functionality is turned on for this task. If true
, execute command functionality is turned on all the containers in the task.
ephemeral_storage: Option<EphemeralStorage>
The amount of ephemeral storage to allocate for the task. This parameter is used to expand the total amount of ephemeral storage available, beyond the default amount, for tasks hosted on Fargate.
runtime_platform: Option<RuntimePlatform>
An object that represents the compute environment architecture for Batch jobs on Fargate.
repository_credentials: Option<RepositoryCredentials>
The private repository authentication credentials to use.
Implementations§
Source§impl ContainerProperties
impl ContainerProperties
Sourcepub fn image(&self) -> Option<&str>
pub fn image(&self) -> Option<&str>
Required. The image used to start a container. This string is passed directly to the Docker daemon. Images in the Docker Hub registry are available by default. Other repositories are specified with repository-url/image:tag
. It can be 255 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), underscores (_), colons (:), periods (.), forward slashes (/), and number signs (#). This parameter maps to Image
in the Create a container section of the Docker Remote API and the IMAGE
parameter of docker run.
Docker image architecture must match the processor architecture of the compute resources that they're scheduled on. For example, ARM-based Docker images can only run on ARM-based compute resources.
-
Images in Amazon ECR Public repositories use the full
registry/repository\[:tag\]
orregistry/repository\[@digest\]
naming conventions. For example,public.ecr.aws/registry_alias/my-web-app:latest
. -
Images in Amazon ECR repositories use the full registry and repository URI (for example,
123456789012.dkr.ecr.
)..amazonaws.com/ -
Images in official repositories on Docker Hub use a single name (for example,
ubuntu
ormongo
). -
Images in other repositories on Docker Hub are qualified with an organization name (for example,
amazon/amazon-ecs-agent
). -
Images in other online repositories are qualified further by a domain name (for example,
quay.io/assemblyline/ubuntu
).
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 specify the vCPU requirements for the job definition. It's not supported for jobs running on Fargate resources. For jobs running on Amazon EC2 resources, it specifies the number of vCPUs reserved for the job.
Each vCPU is equivalent to 1,024 CPU shares. This parameter maps to CpuShares
in the Create a container section of the Docker Remote API and the --cpu-shares
option to docker run. The number of vCPUs must be specified but can be specified in several places. You must specify it at least once for each node.
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 specify the memory requirements for the job definition. It's not supported for jobs running on Fargate resources. For jobs that run on Amazon EC2 resources, it specifies the memory hard limit (in MiB) for a container. If your container attempts to exceed the specified number, it's terminated. You must specify at least 4 MiB of memory for a job using this parameter. The memory hard limit can be specified in several places. It must be specified for each node at least once.
Sourcepub fn command(&self) -> &[String]
pub fn command(&self) -> &[String]
The command that's passed to the container. This parameter maps to Cmd
in the Create a container section of the Docker Remote API and the COMMAND
parameter to docker run. For more information, see https://docs.docker.com/engine/reference/builder/#cmd.
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 job_role_arn(&self) -> Option<&str>
pub fn job_role_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the IAM role that the container can assume for Amazon Web Services permissions. For more information, see IAM roles for tasks in the Amazon Elastic Container Service Developer Guide.
Sourcepub fn execution_role_arn(&self) -> Option<&str>
pub fn execution_role_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the execution role that Batch can assume. For jobs that run on Fargate resources, you must provide an execution role. For more information, see Batch execution IAM role in the Batch User Guide.
Sourcepub fn volumes(&self) -> &[Volume]
pub fn volumes(&self) -> &[Volume]
A list of data volumes used in a job.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .volumes.is_none()
.
Sourcepub fn environment(&self) -> &[KeyValuePair]
pub fn environment(&self) -> &[KeyValuePair]
The environment variables to pass to a container. This parameter maps to Env
in the Create a container section of the Docker Remote API and the --env
option to docker run.
We don't recommend using plaintext environment variables for sensitive information, such as credential data.
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 mount_points(&self) -> &[MountPoint]
pub fn mount_points(&self) -> &[MountPoint]
The mount points for data volumes in your container. This parameter maps to Volumes
in the Create a container section of the Docker Remote API and the --volume
option to docker run.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .mount_points.is_none()
.
Sourcepub fn readonly_root_filesystem(&self) -> Option<bool>
pub fn readonly_root_filesystem(&self) -> Option<bool>
When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs
in the Create a container section of the Docker Remote API and the --read-only
option to docker run
.
Sourcepub fn privileged(&self) -> Option<bool>
pub fn privileged(&self) -> Option<bool>
When this parameter is true, the container is given elevated permissions on the host container instance (similar to the root
user). This parameter maps to Privileged
in the Create a container section of the Docker Remote API and the --privileged
option to docker run. The default value is false.
This parameter isn't applicable to jobs that are running on Fargate resources and shouldn't be provided, or specified as false.
Sourcepub fn ulimits(&self) -> &[Ulimit]
pub fn ulimits(&self) -> &[Ulimit]
A list of ulimits
to set in the container. This parameter maps to Ulimits
in the Create a container section of the Docker Remote API and the --ulimit
option to docker run.
This parameter isn't applicable to jobs that are running on Fargate resources and shouldn't be provided.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .ulimits.is_none()
.
Sourcepub fn user(&self) -> Option<&str>
pub fn user(&self) -> Option<&str>
The user name to use inside the container. This parameter maps to User
in the Create a container section of the Docker Remote API and the --user
option to docker run.
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. All node groups in a multi-node parallel job must use the same instance type.
This parameter isn't applicable to single-node container jobs or jobs that run on Fargate resources, and shouldn't be provided.
Sourcepub fn resource_requirements(&self) -> &[ResourceRequirement]
pub fn resource_requirements(&self) -> &[ResourceRequirement]
The type and amount of resources to assign to a container. 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()
.
Sourcepub fn linux_parameters(&self) -> Option<&LinuxParameters>
pub fn linux_parameters(&self) -> Option<&LinuxParameters>
Linux-specific modifications that are applied to the container, such as details for device mappings.
Sourcepub fn log_configuration(&self) -> Option<&LogConfiguration>
pub fn log_configuration(&self) -> Option<&LogConfiguration>
The log configuration specification for the container.
This parameter maps to LogConfig
in the Create a container section of the Docker Remote API and the --log-driver
option to docker run. By default, containers use the same logging driver that the Docker daemon uses. However the container might use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance (or on a different log server for remote logging options). For more information on the options for different supported log drivers, see Configure logging drivers in the Docker documentation.
Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type).
This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version | grep "Server API version"
The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS
environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide.
Sourcepub fn secrets(&self) -> &[Secret]
pub fn secrets(&self) -> &[Secret]
The secrets for the container. For more information, see Specifying sensitive data in the Batch User Guide.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .secrets.is_none()
.
Sourcepub fn network_configuration(&self) -> Option<&NetworkConfiguration>
pub fn network_configuration(&self) -> Option<&NetworkConfiguration>
The network configuration for jobs that are running on Fargate resources. Jobs that are running on Amazon EC2 resources must not specify this parameter.
Sourcepub fn fargate_platform_configuration(
&self,
) -> Option<&FargatePlatformConfiguration>
pub fn fargate_platform_configuration( &self, ) -> Option<&FargatePlatformConfiguration>
The platform configuration for jobs that are running on Fargate resources. Jobs that are running on Amazon EC2 resources must not specify this parameter.
Sourcepub fn enable_execute_command(&self) -> Option<bool>
pub fn enable_execute_command(&self) -> Option<bool>
Determines whether execute command functionality is turned on for this task. If true
, execute command functionality is turned on all the containers in the task.
Sourcepub fn ephemeral_storage(&self) -> Option<&EphemeralStorage>
pub fn ephemeral_storage(&self) -> Option<&EphemeralStorage>
The amount of ephemeral storage to allocate for the task. This parameter is used to expand the total amount of ephemeral storage available, beyond the default amount, for tasks hosted on Fargate.
Sourcepub fn runtime_platform(&self) -> Option<&RuntimePlatform>
pub fn runtime_platform(&self) -> Option<&RuntimePlatform>
An object that represents the compute environment architecture for Batch jobs on Fargate.
Sourcepub fn repository_credentials(&self) -> Option<&RepositoryCredentials>
pub fn repository_credentials(&self) -> Option<&RepositoryCredentials>
The private repository authentication credentials to use.
Source§impl ContainerProperties
impl ContainerProperties
Sourcepub fn builder() -> ContainerPropertiesBuilder
pub fn builder() -> ContainerPropertiesBuilder
Creates a new builder-style object to manufacture ContainerProperties
.
Trait Implementations§
Source§impl Clone for ContainerProperties
impl Clone for ContainerProperties
Source§fn clone(&self) -> ContainerProperties
fn clone(&self) -> ContainerProperties
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for ContainerProperties
impl Debug for ContainerProperties
Source§impl PartialEq for ContainerProperties
impl PartialEq for ContainerProperties
impl StructuralPartialEq for ContainerProperties
Auto Trait Implementations§
impl Freeze for ContainerProperties
impl RefUnwindSafe for ContainerProperties
impl Send for ContainerProperties
impl Sync for ContainerProperties
impl Unpin for ContainerProperties
impl UnwindSafe for ContainerProperties
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);