#[non_exhaustive]pub struct Task {Show 37 fields
pub attachments: Option<Vec<Attachment>>,
pub attributes: Option<Vec<Attribute>>,
pub availability_zone: Option<String>,
pub capacity_provider_name: Option<String>,
pub cluster_arn: Option<String>,
pub connectivity: Option<Connectivity>,
pub connectivity_at: Option<DateTime>,
pub container_instance_arn: Option<String>,
pub containers: Option<Vec<Container>>,
pub cpu: Option<String>,
pub created_at: Option<DateTime>,
pub desired_status: Option<String>,
pub enable_execute_command: bool,
pub execution_stopped_at: Option<DateTime>,
pub group: Option<String>,
pub health_status: Option<HealthStatus>,
pub inference_accelerators: Option<Vec<InferenceAccelerator>>,
pub last_status: Option<String>,
pub launch_type: Option<LaunchType>,
pub memory: Option<String>,
pub overrides: Option<TaskOverride>,
pub platform_version: Option<String>,
pub platform_family: Option<String>,
pub pull_started_at: Option<DateTime>,
pub pull_stopped_at: Option<DateTime>,
pub started_at: Option<DateTime>,
pub started_by: Option<String>,
pub stop_code: Option<TaskStopCode>,
pub stopped_at: Option<DateTime>,
pub stopped_reason: Option<String>,
pub stopping_at: Option<DateTime>,
pub tags: Option<Vec<Tag>>,
pub task_arn: Option<String>,
pub task_definition_arn: Option<String>,
pub version: i64,
pub ephemeral_storage: Option<EphemeralStorage>,
pub fargate_ephemeral_storage: Option<TaskEphemeralStorage>,
}
Expand description
Details on a task in a cluster.
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.attachments: Option<Vec<Attachment>>
The Elastic Network Adapter that's associated with the task if the task uses the awsvpc
network mode.
attributes: Option<Vec<Attribute>>
The attributes of the task
availability_zone: Option<String>
The Availability Zone for the task.
capacity_provider_name: Option<String>
The capacity provider that's associated with the task.
cluster_arn: Option<String>
The ARN of the cluster that hosts the task.
connectivity: Option<Connectivity>
The connectivity status of a task.
connectivity_at: Option<DateTime>
The Unix timestamp for the time when the task last went into CONNECTED
status.
container_instance_arn: Option<String>
The ARN of the container instances that host the task.
containers: Option<Vec<Container>>
The containers that's associated with the task.
cpu: Option<String>
The number of CPU units used by the task as expressed in a task definition. It can be expressed as an integer using CPU units (for example, 1024
). It can also be expressed as a string using vCPUs (for example, 1 vCPU
or 1 vcpu
). String values are converted to an integer that indicates the CPU units when the task definition is registered.
If you're using the EC2 launch type or the external launch type, this field is optional. Supported values are between 128
CPU units (0.125
vCPUs) and 196608
CPU units (192
vCPUs). If you do not specify a value, the parameter is ignored.
This field is required for Fargate. For information about the valid values, see Task size in the Amazon Elastic Container Service Developer Guide.
created_at: Option<DateTime>
The Unix timestamp for the time when the task was created. More specifically, it's for the time when the task entered the PENDING
state.
desired_status: Option<String>
The desired status of the task. For more information, see Task Lifecycle.
enable_execute_command: 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.
execution_stopped_at: Option<DateTime>
The Unix timestamp for the time when the task execution stopped.
group: Option<String>
The name of the task group that's associated with the task.
health_status: Option<HealthStatus>
The health status for the task. It's determined by the health of the essential containers in the task. If all essential containers in the task are reporting as HEALTHY
, the task status also reports as HEALTHY
. If any essential containers in the task are reporting as UNHEALTHY
or UNKNOWN
, the task status also reports as UNHEALTHY
or UNKNOWN
.
The Amazon ECS container agent doesn't monitor or report on Docker health checks that are embedded in a container image and not specified in the container definition. For example, this includes those specified in a parent image or from the image's Dockerfile. Health check parameters that are specified in a container definition override any Docker health checks that are found in the container image.
inference_accelerators: Option<Vec<InferenceAccelerator>>
The Elastic Inference accelerator that's associated with the task.
last_status: Option<String>
The last known status for the task. For more information, see Task Lifecycle.
launch_type: Option<LaunchType>
The infrastructure where your task runs on. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
memory: Option<String>
The amount of memory (in MiB) that the task uses as expressed in a task definition. It can be expressed as an integer using MiB (for example, 1024
). If it's expressed as a string using GB (for example, 1GB
or 1 GB
), it's converted to an integer indicating the MiB when the task definition is registered.
If you use the EC2 launch type, this field is optional.
If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines the range of supported values for the cpu
parameter.
-
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available
cpu
values: 256 (.25 vCPU) -
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available
cpu
values: 512 (.5 vCPU) -
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu
values: 1024 (1 vCPU) -
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available
cpu
values: 2048 (2 vCPU) -
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available
cpu
values: 4096 (4 vCPU) -
Between 16 GB and 60 GB in 4 GB increments - Available
cpu
values: 8192 (8 vCPU)This option requires Linux platform
1.4.0
or later. -
Between 32GB and 120 GB in 8 GB increments - Available
cpu
values: 16384 (16 vCPU)This option requires Linux platform
1.4.0
or later.
overrides: Option<TaskOverride>
One or more container overrides.
platform_version: Option<String>
The platform version where your task runs on. A platform version is only specified for tasks that use the Fargate launch type. If you didn't specify one, the LATEST
platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.
platform_family: Option<String>
The operating system that your tasks are running on. A platform family is specified only for tasks that use the Fargate launch type.
All tasks that run as part of this service must use the same platformFamily
value as the service (for example, LINUX.
).
pull_started_at: Option<DateTime>
The Unix timestamp for the time when the container image pull began.
pull_stopped_at: Option<DateTime>
The Unix timestamp for the time when the container image pull completed.
started_at: Option<DateTime>
The Unix timestamp for the time when the task started. More specifically, it's for the time when the task transitioned from the PENDING
state to the RUNNING
state.
started_by: Option<String>
The tag specified when a task is started. If an Amazon ECS service started the task, the startedBy
parameter contains the deployment ID of that service.
stop_code: Option<TaskStopCode>
The stop code indicating why a task was stopped. The stoppedReason
might contain additional details.
For more information about stop code, see Stopped tasks error codes in the Amazon ECS Developer Guide.
stopped_at: Option<DateTime>
The Unix timestamp for the time when the task was stopped. More specifically, it's for the time when the task transitioned from the RUNNING
state to the STOPPED
state.
stopped_reason: Option<String>
The reason that the task was stopped.
stopping_at: Option<DateTime>
The Unix timestamp for the time when the task stops. More specifically, it's for the time when the task transitions from the RUNNING
state to STOPPING
.
The metadata that you apply to the task to help you categorize and organize the task. Each tag consists of a key and an optional value. You define both the key and value.
The following basic restrictions apply to tags:
-
Maximum number of tags per resource - 50
-
For each resource, each tag key must be unique, and each tag key can have only one value.
-
Maximum key length - 128 Unicode characters in UTF-8
-
Maximum value length - 256 Unicode characters in UTF-8
-
If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
-
Tag keys and values are case-sensitive.
-
Do not use
aws:
,AWS:
, or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.
task_arn: Option<String>
The Amazon Resource Name (ARN) of the task.
task_definition_arn: Option<String>
The ARN of the task definition that creates the task.
version: i64
The version counter for the task. Every time a task experiences a change that starts a CloudWatch event, the version counter is incremented. If you replicate your Amazon ECS task state with CloudWatch Events, you can compare the version of a task reported by the Amazon ECS API actions with the version reported in CloudWatch Events for the task (inside the detail
object) to verify that the version in your event stream is current.
ephemeral_storage: Option<EphemeralStorage>
The ephemeral storage settings for the task.
fargate_ephemeral_storage: Option<TaskEphemeralStorage>
The Fargate ephemeral storage settings for the task.
Implementations§
Source§impl Task
impl Task
Sourcepub fn attachments(&self) -> &[Attachment]
pub fn attachments(&self) -> &[Attachment]
The Elastic Network Adapter that's associated with the task if the task uses the awsvpc
network mode.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .attachments.is_none()
.
Sourcepub fn attributes(&self) -> &[Attribute]
pub fn attributes(&self) -> &[Attribute]
The attributes of the task
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .attributes.is_none()
.
Sourcepub fn availability_zone(&self) -> Option<&str>
pub fn availability_zone(&self) -> Option<&str>
The Availability Zone for the task.
Sourcepub fn capacity_provider_name(&self) -> Option<&str>
pub fn capacity_provider_name(&self) -> Option<&str>
The capacity provider that's associated with the task.
Sourcepub fn cluster_arn(&self) -> Option<&str>
pub fn cluster_arn(&self) -> Option<&str>
The ARN of the cluster that hosts the task.
Sourcepub fn connectivity(&self) -> Option<&Connectivity>
pub fn connectivity(&self) -> Option<&Connectivity>
The connectivity status of a task.
Sourcepub fn connectivity_at(&self) -> Option<&DateTime>
pub fn connectivity_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task last went into CONNECTED
status.
Sourcepub fn container_instance_arn(&self) -> Option<&str>
pub fn container_instance_arn(&self) -> Option<&str>
The ARN of the container instances that host the task.
Sourcepub fn containers(&self) -> &[Container]
pub fn containers(&self) -> &[Container]
The containers that's associated with the task.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .containers.is_none()
.
Sourcepub fn cpu(&self) -> Option<&str>
pub fn cpu(&self) -> Option<&str>
The number of CPU units used by the task as expressed in a task definition. It can be expressed as an integer using CPU units (for example, 1024
). It can also be expressed as a string using vCPUs (for example, 1 vCPU
or 1 vcpu
). String values are converted to an integer that indicates the CPU units when the task definition is registered.
If you're using the EC2 launch type or the external launch type, this field is optional. Supported values are between 128
CPU units (0.125
vCPUs) and 196608
CPU units (192
vCPUs). If you do not specify a value, the parameter is ignored.
This field is required for Fargate. For information about the valid values, see Task size in the Amazon Elastic Container Service Developer Guide.
Sourcepub fn created_at(&self) -> Option<&DateTime>
pub fn created_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task was created. More specifically, it's for the time when the task entered the PENDING
state.
Sourcepub fn desired_status(&self) -> Option<&str>
pub fn desired_status(&self) -> Option<&str>
The desired status of the task. For more information, see Task Lifecycle.
Sourcepub fn enable_execute_command(&self) -> bool
pub fn enable_execute_command(&self) -> 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 execution_stopped_at(&self) -> Option<&DateTime>
pub fn execution_stopped_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task execution stopped.
Sourcepub fn group(&self) -> Option<&str>
pub fn group(&self) -> Option<&str>
The name of the task group that's associated with the task.
Sourcepub fn health_status(&self) -> Option<&HealthStatus>
pub fn health_status(&self) -> Option<&HealthStatus>
The health status for the task. It's determined by the health of the essential containers in the task. If all essential containers in the task are reporting as HEALTHY
, the task status also reports as HEALTHY
. If any essential containers in the task are reporting as UNHEALTHY
or UNKNOWN
, the task status also reports as UNHEALTHY
or UNKNOWN
.
The Amazon ECS container agent doesn't monitor or report on Docker health checks that are embedded in a container image and not specified in the container definition. For example, this includes those specified in a parent image or from the image's Dockerfile. Health check parameters that are specified in a container definition override any Docker health checks that are found in the container image.
Sourcepub fn inference_accelerators(&self) -> &[InferenceAccelerator]
pub fn inference_accelerators(&self) -> &[InferenceAccelerator]
The Elastic Inference accelerator that's associated with the task.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .inference_accelerators.is_none()
.
Sourcepub fn last_status(&self) -> Option<&str>
pub fn last_status(&self) -> Option<&str>
The last known status for the task. For more information, see Task Lifecycle.
Sourcepub fn launch_type(&self) -> Option<&LaunchType>
pub fn launch_type(&self) -> Option<&LaunchType>
The infrastructure where your task runs on. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
Sourcepub fn memory(&self) -> Option<&str>
pub fn memory(&self) -> Option<&str>
The amount of memory (in MiB) that the task uses as expressed in a task definition. It can be expressed as an integer using MiB (for example, 1024
). If it's expressed as a string using GB (for example, 1GB
or 1 GB
), it's converted to an integer indicating the MiB when the task definition is registered.
If you use the EC2 launch type, this field is optional.
If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines the range of supported values for the cpu
parameter.
-
512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available
cpu
values: 256 (.25 vCPU) -
1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available
cpu
values: 512 (.5 vCPU) -
2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available
cpu
values: 1024 (1 vCPU) -
Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available
cpu
values: 2048 (2 vCPU) -
Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available
cpu
values: 4096 (4 vCPU) -
Between 16 GB and 60 GB in 4 GB increments - Available
cpu
values: 8192 (8 vCPU)This option requires Linux platform
1.4.0
or later. -
Between 32GB and 120 GB in 8 GB increments - Available
cpu
values: 16384 (16 vCPU)This option requires Linux platform
1.4.0
or later.
Sourcepub fn overrides(&self) -> Option<&TaskOverride>
pub fn overrides(&self) -> Option<&TaskOverride>
One or more container overrides.
Sourcepub fn platform_version(&self) -> Option<&str>
pub fn platform_version(&self) -> Option<&str>
The platform version where your task runs on. A platform version is only specified for tasks that use the Fargate launch type. If you didn't specify one, the LATEST
platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.
Sourcepub fn platform_family(&self) -> Option<&str>
pub fn platform_family(&self) -> Option<&str>
The operating system that your tasks are running on. A platform family is specified only for tasks that use the Fargate launch type.
All tasks that run as part of this service must use the same platformFamily
value as the service (for example, LINUX.
).
Sourcepub fn pull_started_at(&self) -> Option<&DateTime>
pub fn pull_started_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the container image pull began.
Sourcepub fn pull_stopped_at(&self) -> Option<&DateTime>
pub fn pull_stopped_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the container image pull completed.
Sourcepub fn started_at(&self) -> Option<&DateTime>
pub fn started_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task started. More specifically, it's for the time when the task transitioned from the PENDING
state to the RUNNING
state.
Sourcepub fn started_by(&self) -> Option<&str>
pub fn started_by(&self) -> Option<&str>
The tag specified when a task is started. If an Amazon ECS service started the task, the startedBy
parameter contains the deployment ID of that service.
Sourcepub fn stop_code(&self) -> Option<&TaskStopCode>
pub fn stop_code(&self) -> Option<&TaskStopCode>
The stop code indicating why a task was stopped. The stoppedReason
might contain additional details.
For more information about stop code, see Stopped tasks error codes in the Amazon ECS Developer Guide.
Sourcepub fn stopped_at(&self) -> Option<&DateTime>
pub fn stopped_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task was stopped. More specifically, it's for the time when the task transitioned from the RUNNING
state to the STOPPED
state.
Sourcepub fn stopped_reason(&self) -> Option<&str>
pub fn stopped_reason(&self) -> Option<&str>
The reason that the task was stopped.
Sourcepub fn stopping_at(&self) -> Option<&DateTime>
pub fn stopping_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task stops. More specifically, it's for the time when the task transitions from the RUNNING
state to STOPPING
.
The metadata that you apply to the task to help you categorize and organize the task. Each tag consists of a key and an optional value. You define both the key and value.
The following basic restrictions apply to tags:
-
Maximum number of tags per resource - 50
-
For each resource, each tag key must be unique, and each tag key can have only one value.
-
Maximum key length - 128 Unicode characters in UTF-8
-
Maximum value length - 256 Unicode characters in UTF-8
-
If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
-
Tag keys and values are case-sensitive.
-
Do not use
aws:
,AWS:
, or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .tags.is_none()
.
Sourcepub fn task_definition_arn(&self) -> Option<&str>
pub fn task_definition_arn(&self) -> Option<&str>
The ARN of the task definition that creates the task.
Sourcepub fn version(&self) -> i64
pub fn version(&self) -> i64
The version counter for the task. Every time a task experiences a change that starts a CloudWatch event, the version counter is incremented. If you replicate your Amazon ECS task state with CloudWatch Events, you can compare the version of a task reported by the Amazon ECS API actions with the version reported in CloudWatch Events for the task (inside the detail
object) to verify that the version in your event stream is current.
Sourcepub fn ephemeral_storage(&self) -> Option<&EphemeralStorage>
pub fn ephemeral_storage(&self) -> Option<&EphemeralStorage>
The ephemeral storage settings for the task.
Sourcepub fn fargate_ephemeral_storage(&self) -> Option<&TaskEphemeralStorage>
pub fn fargate_ephemeral_storage(&self) -> Option<&TaskEphemeralStorage>
The Fargate ephemeral storage settings for the task.
Trait Implementations§
impl StructuralPartialEq for Task
Auto Trait Implementations§
impl Freeze for Task
impl RefUnwindSafe for Task
impl Send for Task
impl Sync for Task
impl Unpin for Task
impl UnwindSafe for Task
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);