#[non_exhaustive]pub struct TaskSet {Show 25 fields
pub id: Option<String>,
pub task_set_arn: Option<String>,
pub service_arn: Option<String>,
pub cluster_arn: Option<String>,
pub started_by: Option<String>,
pub external_id: Option<String>,
pub status: Option<String>,
pub task_definition: Option<String>,
pub computed_desired_count: i32,
pub pending_count: i32,
pub running_count: i32,
pub created_at: Option<DateTime>,
pub updated_at: Option<DateTime>,
pub launch_type: Option<LaunchType>,
pub capacity_provider_strategy: Option<Vec<CapacityProviderStrategyItem>>,
pub platform_version: Option<String>,
pub platform_family: Option<String>,
pub network_configuration: Option<NetworkConfiguration>,
pub load_balancers: Option<Vec<LoadBalancer>>,
pub service_registries: Option<Vec<ServiceRegistry>>,
pub scale: Option<Scale>,
pub stability_status: Option<StabilityStatus>,
pub stability_status_at: Option<DateTime>,
pub tags: Option<Vec<Tag>>,
pub fargate_ephemeral_storage: Option<DeploymentEphemeralStorage>,
}
Expand description
Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL
deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.
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.id: Option<String>
The ID of the task set.
task_set_arn: Option<String>
The Amazon Resource Name (ARN) of the task set.
service_arn: Option<String>
The Amazon Resource Name (ARN) of the service the task set exists in.
cluster_arn: Option<String>
The Amazon Resource Name (ARN) of the cluster that the service that hosts the task set exists in.
started_by: Option<String>
The tag specified when a task set is started. If an CodeDeploy deployment created the task set, the startedBy
parameter is CODE_DEPLOY
. If an external deployment created the task set, the startedBy
field isn't used.
external_id: Option<String>
The external ID associated with the task set.
If an CodeDeploy deployment created a task set, the externalId
parameter contains the CodeDeploy deployment ID.
If a task set is created for an external deployment and is associated with a service discovery registry, the externalId
parameter contains the ECS_TASK_SET_EXTERNAL_ID
Cloud Map attribute.
status: Option<String>
The status of the task set. The following describes each state.
- PRIMARY
-
The task set is serving production traffic.
- ACTIVE
-
The task set isn't serving production traffic.
- DRAINING
-
The tasks in the task set are being stopped, and their corresponding targets are being deregistered from their target group.
task_definition: Option<String>
The task definition that the task set is using.
computed_desired_count: i32
The computed desired count for the task set. This is calculated by multiplying the service's desiredCount
by the task set's scale
percentage. The result is always rounded up. For example, if the computed desired count is 1.2, it rounds up to 2 tasks.
pending_count: i32
The number of tasks in the task set that are in the PENDING
status during a deployment. A task in the PENDING
state is preparing to enter the RUNNING
state. A task set enters the PENDING
status when it launches for the first time or when it's restarted after being in the STOPPED
state.
running_count: i32
The number of tasks in the task set that are in the RUNNING
status during a deployment. A task in the RUNNING
state is running and ready for use.
created_at: Option<DateTime>
The Unix timestamp for the time when the task set was created.
updated_at: Option<DateTime>
The Unix timestamp for the time when the task set was last updated.
launch_type: Option<LaunchType>
The launch type the tasks in the task set are using. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
capacity_provider_strategy: Option<Vec<CapacityProviderStrategyItem>>
The capacity provider strategy that are associated with the task set.
platform_version: Option<String>
The Fargate platform version where the tasks in the task set are running. A platform version is only specified for tasks run on Fargate. 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 in the set are running on. A platform family is specified only for tasks that use the Fargate launch type.
All tasks in the set must have the same value.
network_configuration: Option<NetworkConfiguration>
The network configuration for the task set.
load_balancers: Option<Vec<LoadBalancer>>
Details on a load balancer that are used with a task set.
service_registries: Option<Vec<ServiceRegistry>>
The details for the service discovery registries to assign to this task set. For more information, see Service discovery.
scale: Option<Scale>
A floating-point percentage of your desired number of tasks to place and keep running in the task set.
stability_status: Option<StabilityStatus>
The stability status. This indicates whether the task set has reached a steady state. If the following conditions are met, the task set are in STEADY_STATE
:
-
The task
runningCount
is equal to thecomputedDesiredCount
. -
The
pendingCount
is0
. -
There are no tasks that are running on container instances in the
DRAINING
status. -
All tasks are reporting a healthy status from the load balancers, service discovery, and container health checks.
If any of those conditions aren't met, the stability status returns STABILIZING
.
stability_status_at: Option<DateTime>
The Unix timestamp for the time when the task set stability status was retrieved.
The metadata that you apply to the task set to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.
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.
fargate_ephemeral_storage: Option<DeploymentEphemeralStorage>
The Fargate ephemeral storage settings for the task set.
Implementations§
Source§impl TaskSet
impl TaskSet
Sourcepub fn task_set_arn(&self) -> Option<&str>
pub fn task_set_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the task set.
Sourcepub fn service_arn(&self) -> Option<&str>
pub fn service_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the service the task set exists in.
Sourcepub fn cluster_arn(&self) -> Option<&str>
pub fn cluster_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the cluster that the service that hosts the task set exists in.
Sourcepub fn started_by(&self) -> Option<&str>
pub fn started_by(&self) -> Option<&str>
The tag specified when a task set is started. If an CodeDeploy deployment created the task set, the startedBy
parameter is CODE_DEPLOY
. If an external deployment created the task set, the startedBy
field isn't used.
Sourcepub fn external_id(&self) -> Option<&str>
pub fn external_id(&self) -> Option<&str>
The external ID associated with the task set.
If an CodeDeploy deployment created a task set, the externalId
parameter contains the CodeDeploy deployment ID.
If a task set is created for an external deployment and is associated with a service discovery registry, the externalId
parameter contains the ECS_TASK_SET_EXTERNAL_ID
Cloud Map attribute.
Sourcepub fn status(&self) -> Option<&str>
pub fn status(&self) -> Option<&str>
The status of the task set. The following describes each state.
- PRIMARY
-
The task set is serving production traffic.
- ACTIVE
-
The task set isn't serving production traffic.
- DRAINING
-
The tasks in the task set are being stopped, and their corresponding targets are being deregistered from their target group.
Sourcepub fn task_definition(&self) -> Option<&str>
pub fn task_definition(&self) -> Option<&str>
The task definition that the task set is using.
Sourcepub fn computed_desired_count(&self) -> i32
pub fn computed_desired_count(&self) -> i32
The computed desired count for the task set. This is calculated by multiplying the service's desiredCount
by the task set's scale
percentage. The result is always rounded up. For example, if the computed desired count is 1.2, it rounds up to 2 tasks.
Sourcepub fn pending_count(&self) -> i32
pub fn pending_count(&self) -> i32
The number of tasks in the task set that are in the PENDING
status during a deployment. A task in the PENDING
state is preparing to enter the RUNNING
state. A task set enters the PENDING
status when it launches for the first time or when it's restarted after being in the STOPPED
state.
Sourcepub fn running_count(&self) -> i32
pub fn running_count(&self) -> i32
The number of tasks in the task set that are in the RUNNING
status during a deployment. A task in the RUNNING
state is running and ready for use.
Sourcepub fn created_at(&self) -> Option<&DateTime>
pub fn created_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task set was created.
Sourcepub fn updated_at(&self) -> Option<&DateTime>
pub fn updated_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task set was last updated.
Sourcepub fn launch_type(&self) -> Option<&LaunchType>
pub fn launch_type(&self) -> Option<&LaunchType>
The launch type the tasks in the task set are using. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
Sourcepub fn capacity_provider_strategy(&self) -> &[CapacityProviderStrategyItem]
pub fn capacity_provider_strategy(&self) -> &[CapacityProviderStrategyItem]
The capacity provider strategy that are associated with the task set.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .capacity_provider_strategy.is_none()
.
Sourcepub fn platform_version(&self) -> Option<&str>
pub fn platform_version(&self) -> Option<&str>
The Fargate platform version where the tasks in the task set are running. A platform version is only specified for tasks run on Fargate. 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 in the set are running on. A platform family is specified only for tasks that use the Fargate launch type.
All tasks in the set must have the same value.
Sourcepub fn network_configuration(&self) -> Option<&NetworkConfiguration>
pub fn network_configuration(&self) -> Option<&NetworkConfiguration>
The network configuration for the task set.
Sourcepub fn load_balancers(&self) -> &[LoadBalancer]
pub fn load_balancers(&self) -> &[LoadBalancer]
Details on a load balancer that are used with a task set.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .load_balancers.is_none()
.
Sourcepub fn service_registries(&self) -> &[ServiceRegistry]
pub fn service_registries(&self) -> &[ServiceRegistry]
The details for the service discovery registries to assign to this task set. For more information, see Service discovery.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .service_registries.is_none()
.
Sourcepub fn scale(&self) -> Option<&Scale>
pub fn scale(&self) -> Option<&Scale>
A floating-point percentage of your desired number of tasks to place and keep running in the task set.
Sourcepub fn stability_status(&self) -> Option<&StabilityStatus>
pub fn stability_status(&self) -> Option<&StabilityStatus>
The stability status. This indicates whether the task set has reached a steady state. If the following conditions are met, the task set are in STEADY_STATE
:
-
The task
runningCount
is equal to thecomputedDesiredCount
. -
The
pendingCount
is0
. -
There are no tasks that are running on container instances in the
DRAINING
status. -
All tasks are reporting a healthy status from the load balancers, service discovery, and container health checks.
If any of those conditions aren't met, the stability status returns STABILIZING
.
Sourcepub fn stability_status_at(&self) -> Option<&DateTime>
pub fn stability_status_at(&self) -> Option<&DateTime>
The Unix timestamp for the time when the task set stability status was retrieved.
The metadata that you apply to the task set to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.
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 fargate_ephemeral_storage(&self) -> Option<&DeploymentEphemeralStorage>
pub fn fargate_ephemeral_storage(&self) -> Option<&DeploymentEphemeralStorage>
The Fargate ephemeral storage settings for the task set.
Trait Implementations§
impl StructuralPartialEq for TaskSet
Auto Trait Implementations§
impl Freeze for TaskSet
impl RefUnwindSafe for TaskSet
impl Send for TaskSet
impl Sync for TaskSet
impl Unpin for TaskSet
impl UnwindSafe for TaskSet
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);