#[non_exhaustive]pub struct JobQueueDetail {
pub job_queue_name: Option<String>,
pub job_queue_arn: Option<String>,
pub state: Option<JqState>,
pub scheduling_policy_arn: Option<String>,
pub status: Option<JqStatus>,
pub status_reason: Option<String>,
pub priority: Option<i32>,
pub compute_environment_order: Option<Vec<ComputeEnvironmentOrder>>,
pub tags: Option<HashMap<String, String>>,
pub job_state_time_limit_actions: Option<Vec<JobStateTimeLimitAction>>,
}
Expand description
An object that represents the details for an Batch job queue.
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.job_queue_name: Option<String>
The job queue name.
job_queue_arn: Option<String>
The Amazon Resource Name (ARN) of the job queue.
state: Option<JqState>
Describes the ability of the queue to accept new jobs. If the job queue state is ENABLED
, it can accept jobs. If the job queue state is DISABLED
, new jobs can't be added to the queue, but jobs already in the queue can finish.
scheduling_policy_arn: Option<String>
The Amazon Resource Name (ARN) of the scheduling policy. The format is aws:Partition:batch:Region:Account:scheduling-policy/Name
. For example, aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy
.
status: Option<JqStatus>
The status of the job queue (for example, CREATING
or VALID
).
status_reason: Option<String>
A short, human-readable string to provide additional details for the current status of the job queue.
priority: Option<i32>
The priority of the job queue. Job queue priority determines the order that job queues are evaluated when multiple queues dispatch jobs within a shared compute environment. A higher value for priority
indicates a higher priority. Queues are evaluated in cycles, in descending order by priority. For example, a job queue with a priority value of 10
is evaluated before a queue with a priority value of 1
. All of the compute environments must be either Amazon EC2 (EC2
or SPOT
) or Fargate (FARGATE
or FARGATE_SPOT
). Amazon EC2 and Fargate compute environments can't be mixed.
Job queue priority doesn't guarantee that a particular job executes before a job in a lower priority queue. Jobs added to higher priority queues during the queue evaluation cycle might not be evaluated until the next cycle. A job is dispatched from a queue only if resources are available when the queue is evaluated. If there are insufficient resources available at that time, the cycle proceeds to the next queue. This means that jobs added to higher priority queues might have to wait for jobs in multiple lower priority queues to complete before they are dispatched. You can use job dependencies to control the order for jobs from queues with different priorities. For more information, see Job Dependencies in the Batch User Guide.
compute_environment_order: Option<Vec<ComputeEnvironmentOrder>>
The compute environments that are attached to the job queue and the order that job placement is preferred. Compute environments are selected for job placement in ascending order.
The tags that are applied to the job queue. For more information, see Tagging your Batch resources in Batch User Guide.
job_state_time_limit_actions: Option<Vec<JobStateTimeLimitAction>>
The set of actions that Batch perform on jobs that remain at the head of the job queue in the specified state longer than specified times. Batch will perform each action after maxTimeSeconds
has passed.
Implementations§
Source§impl JobQueueDetail
impl JobQueueDetail
Sourcepub fn job_queue_name(&self) -> Option<&str>
pub fn job_queue_name(&self) -> Option<&str>
The job queue name.
Sourcepub fn job_queue_arn(&self) -> Option<&str>
pub fn job_queue_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the job queue.
Sourcepub fn state(&self) -> Option<&JqState>
pub fn state(&self) -> Option<&JqState>
Describes the ability of the queue to accept new jobs. If the job queue state is ENABLED
, it can accept jobs. If the job queue state is DISABLED
, new jobs can't be added to the queue, but jobs already in the queue can finish.
Sourcepub fn scheduling_policy_arn(&self) -> Option<&str>
pub fn scheduling_policy_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the scheduling policy. The format is aws:Partition:batch:Region:Account:scheduling-policy/Name
. For example, aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy
.
Sourcepub fn status(&self) -> Option<&JqStatus>
pub fn status(&self) -> Option<&JqStatus>
The status of the job queue (for example, CREATING
or VALID
).
Sourcepub fn status_reason(&self) -> Option<&str>
pub fn status_reason(&self) -> Option<&str>
A short, human-readable string to provide additional details for the current status of the job queue.
Sourcepub fn priority(&self) -> Option<i32>
pub fn priority(&self) -> Option<i32>
The priority of the job queue. Job queue priority determines the order that job queues are evaluated when multiple queues dispatch jobs within a shared compute environment. A higher value for priority
indicates a higher priority. Queues are evaluated in cycles, in descending order by priority. For example, a job queue with a priority value of 10
is evaluated before a queue with a priority value of 1
. All of the compute environments must be either Amazon EC2 (EC2
or SPOT
) or Fargate (FARGATE
or FARGATE_SPOT
). Amazon EC2 and Fargate compute environments can't be mixed.
Job queue priority doesn't guarantee that a particular job executes before a job in a lower priority queue. Jobs added to higher priority queues during the queue evaluation cycle might not be evaluated until the next cycle. A job is dispatched from a queue only if resources are available when the queue is evaluated. If there are insufficient resources available at that time, the cycle proceeds to the next queue. This means that jobs added to higher priority queues might have to wait for jobs in multiple lower priority queues to complete before they are dispatched. You can use job dependencies to control the order for jobs from queues with different priorities. For more information, see Job Dependencies in the Batch User Guide.
Sourcepub fn compute_environment_order(&self) -> &[ComputeEnvironmentOrder]
pub fn compute_environment_order(&self) -> &[ComputeEnvironmentOrder]
The compute environments that are attached to the job queue and the order that job placement is preferred. Compute environments are selected for job placement in ascending order.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .compute_environment_order.is_none()
.
The tags that are applied to the job queue. For more information, see Tagging your Batch resources in Batch User Guide.
Sourcepub fn job_state_time_limit_actions(&self) -> &[JobStateTimeLimitAction]
pub fn job_state_time_limit_actions(&self) -> &[JobStateTimeLimitAction]
The set of actions that Batch perform on jobs that remain at the head of the job queue in the specified state longer than specified times. Batch will perform each action after maxTimeSeconds
has passed.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .job_state_time_limit_actions.is_none()
.
Source§impl JobQueueDetail
impl JobQueueDetail
Sourcepub fn builder() -> JobQueueDetailBuilder
pub fn builder() -> JobQueueDetailBuilder
Creates a new builder-style object to manufacture JobQueueDetail
.
Trait Implementations§
Source§impl Clone for JobQueueDetail
impl Clone for JobQueueDetail
Source§fn clone(&self) -> JobQueueDetail
fn clone(&self) -> JobQueueDetail
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for JobQueueDetail
impl Debug for JobQueueDetail
Source§impl PartialEq for JobQueueDetail
impl PartialEq for JobQueueDetail
impl StructuralPartialEq for JobQueueDetail
Auto Trait Implementations§
impl Freeze for JobQueueDetail
impl RefUnwindSafe for JobQueueDetail
impl Send for JobQueueDetail
impl Sync for JobQueueDetail
impl Unpin for JobQueueDetail
impl UnwindSafe for JobQueueDetail
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);