Struct aws_sdk_batch::input::CreateJobQueueInput

#[non_exhaustive]
pub struct CreateJobQueueInput {
    pub job_queue_name: Option<String>,
    pub state: Option<JqState>,
    pub priority: i32,
    pub compute_environment_order: Option<Vec<ComputeEnvironmentOrder>>,
    pub tags: Option<HashMap<String, String>>,
}

Contains the parameters for CreateJobQueue.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

job_queue_name: Option<String>

The name of the job queue. Up to 128 letters (uppercase and lowercase), numbers, and underscores are allowed.

state: Option<JqState>

The state of the job queue. If the job queue state is ENABLED, it is able to 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.

priority: i32

The priority of the job queue. Job queues with a higher priority (or a higher integer value for the priority parameter) are evaluated first when associated with the same compute environment. Priority is determined in descending order. For example, a job queue with a priority value of 10 is given scheduling preference over a job queue with a priority value of 1. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can't be mixed.

compute_environment_order: Option<Vec<ComputeEnvironmentOrder>>

The set of compute environments mapped to a job queue and their order relative to each other. The job scheduler uses this parameter to determine which compute environment should run a specific job. Compute environments must be in the VALID state before you can associate them with a job queue. You can associate up to three compute environments with a job queue. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can't be mixed.

All compute environments that are associated with a job queue must share the same architecture. Batch doesn't support mixing compute environment architecture types in a single job queue.

tags: Option<HashMap<String, String>>

The tags that you apply to the job queue to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging your Batch resources in Batch User Guide.

Implementations

impl CreateJobQueueInput

pub async fn make_operation(
    &self,
    _config: &Config
) -> Result<Operation<CreateJobQueue, AwsErrorRetryPolicy>, BuildError>

Consumes the builder and constructs an Operation<CreateJobQueue>

pub fn builder() -> Builder

Creates a new builder-style object to manufacture CreateJobQueueInput

impl CreateJobQueueInput

pub fn job_queue_name(&self) -> Option<&str>

The name of the job queue. Up to 128 letters (uppercase and lowercase), numbers, and underscores are allowed.

pub fn state(&self) -> Option<&JqState>

The state of the job queue. If the job queue state is ENABLED, it is able to 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.

pub fn priority(&self) -> i32

The priority of the job queue. Job queues with a higher priority (or a higher integer value for the priority parameter) are evaluated first when associated with the same compute environment. Priority is determined in descending order. For example, a job queue with a priority value of 10 is given scheduling preference over a job queue with a priority value of 1. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can't be mixed.

pub fn compute_environment_order(&self) -> Option<&[ComputeEnvironmentOrder]>

The set of compute environments mapped to a job queue and their order relative to each other. The job scheduler uses this parameter to determine which compute environment should run a specific job. Compute environments must be in the VALID state before you can associate them with a job queue. You can associate up to three compute environments with a job queue. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can't be mixed.

All compute environments that are associated with a job queue must share the same architecture. Batch doesn't support mixing compute environment architecture types in a single job queue.

pub fn tags(&self) -> Option<&HashMap<String, String>>

The tags that you apply to the job queue to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging your Batch resources in Batch User Guide.

Trait Implementations

impl Clone for CreateJobQueueInput

fn clone(&self) -> CreateJobQueueInput

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreateJobQueueInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq<CreateJobQueueInput> for CreateJobQueueInput

fn eq(&self, other: &CreateJobQueueInput) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &CreateJobQueueInput) -> bool

This method tests for !=.

impl StructuralPartialEq for CreateJobQueueInput