#[non_exhaustive]pub struct CreateAssociationBatchRequestEntry {Show 20 fields
pub name: String,
pub instance_id: Option<String>,
pub parameters: Option<HashMap<String, Vec<String>>>,
pub automation_target_parameter_name: Option<String>,
pub document_version: Option<String>,
pub targets: Option<Vec<Target>>,
pub schedule_expression: Option<String>,
pub output_location: Option<InstanceAssociationOutputLocation>,
pub association_name: Option<String>,
pub max_errors: Option<String>,
pub max_concurrency: Option<String>,
pub compliance_severity: Option<AssociationComplianceSeverity>,
pub sync_compliance: Option<AssociationSyncCompliance>,
pub apply_only_at_cron_interval: bool,
pub calendar_names: Option<Vec<String>>,
pub target_locations: Option<Vec<TargetLocation>>,
pub schedule_offset: Option<i32>,
pub duration: Option<i32>,
pub target_maps: Option<Vec<HashMap<String, Vec<String>>>>,
pub alarm_configuration: Option<AlarmConfiguration>,
}
Expand description
Describes the association of a Amazon Web Services Systems Manager document (SSM document) and a managed node.
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.name: String
The name of the SSM document that contains the configuration information for the managed node. You can specify Command or Automation runbooks.
You can specify Amazon Web Services-predefined documents, documents you created, or a document that is shared with you from another account.
For SSM documents that are shared with you from other Amazon Web Services accounts, you must specify the complete SSM document ARN, in the following format:
arn:aws:ssm:region:account-id:document/document-name
For example:
arn:aws:ssm:us-east-2:12345678912:document/My-Shared-Document
For Amazon Web Services-predefined documents and SSM documents you created in your account, you only need to specify the document name. For example, AWS-ApplyPatchBaseline
or My-Document
.
instance_id: Option<String>
The managed node ID.
InstanceId
has been deprecated. To specify a managed node ID for an association, use the Targets
parameter. Requests that include the parameter InstanceID
with Systems Manager documents (SSM documents) that use schema version 2.0 or later will fail. In addition, if you use the parameter InstanceId
, you can't use the parameters AssociationName
, DocumentVersion
, MaxErrors
, MaxConcurrency
, OutputLocation
, or ScheduleExpression
. To use these parameters, you must use the Targets
parameter.
parameters: Option<HashMap<String, Vec<String>>>
A description of the parameters for a document.
automation_target_parameter_name: Option<String>
Specify the target for the association. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a tool in Amazon Web Services Systems Manager.
document_version: Option<String>
The document version.
targets: Option<Vec<Target>>
The managed nodes targeted by the request.
schedule_expression: Option<String>
A cron expression that specifies a schedule when the association runs.
output_location: Option<InstanceAssociationOutputLocation>
An S3 bucket where you want to store the results of this request.
association_name: Option<String>
Specify a descriptive name for the association.
max_errors: Option<String>
The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set MaxError
to 10%, then the system stops sending the request when the sixth error is received.
Executions that are already running an association when MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, set MaxConcurrency
to 1 so that executions proceed one at a time.
max_concurrency: Option<String>
The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified for MaxConcurrency
.
compliance_severity: Option<AssociationComplianceSeverity>
The severity level to assign to the association.
sync_compliance: Option<AssociationSyncCompliance>
The mode for generating association compliance. You can specify AUTO
or MANUAL
. In AUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association is COMPLIANT
. If the association execution doesn't run successfully, the association is NON-COMPLIANT
.
In MANUAL
mode, you must specify the AssociationId
as a parameter for the PutComplianceItems
API operation. In this case, compliance data isn't managed by State Manager, a tool in Amazon Web Services Systems Manager. It is managed by your direct call to the PutComplianceItems
API operation.
By default, all associations use AUTO
mode.
apply_only_at_cron_interval: bool
By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified and when target changes are detected. Specify true
for ApplyOnlyAtCronInterval
if you want the association to run only according to the schedule you specified.
For more information, see Understanding when associations are applied to resources and >About target updates with Automation runbooks in the Amazon Web Services Systems Manager User Guide.
This parameter isn't supported for rate expressions.
calendar_names: Option<Vec<String>>
The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see Amazon Web Services Systems Manager Change Calendar in the Amazon Web Services Systems Manager User Guide.
target_locations: Option<Vec<TargetLocation>>
Use this action to create an association in multiple Regions and multiple accounts.
schedule_offset: Option<i32>
Number of days to wait after the scheduled day to run an association.
duration: Option<i32>
The number of hours the association can run before it is canceled. Duration applies to associations that are currently running, and any pending and in progress commands on all targets. If a target was taken offline for the association to run, it is made available again immediately, without a reboot.
The Duration
parameter applies only when both these conditions are true:
-
The association for which you specify a duration is cancelable according to the parameters of the SSM command document or Automation runbook associated with this execution.
-
The command specifies the
ApplyOnlyAtCronInterval
parameter, which means that the association doesn't run immediately after it is created, but only according to the specified schedule.
target_maps: Option<Vec<HashMap<String, Vec<String>>>>
A key-value mapping of document parameters to target resources. Both Targets and TargetMaps can't be specified together.
alarm_configuration: Option<AlarmConfiguration>
The details for the CloudWatch alarm you want to apply to an automation or command.
Implementations§
Source§impl CreateAssociationBatchRequestEntry
impl CreateAssociationBatchRequestEntry
Sourcepub fn name(&self) -> &str
pub fn name(&self) -> &str
The name of the SSM document that contains the configuration information for the managed node. You can specify Command or Automation runbooks.
You can specify Amazon Web Services-predefined documents, documents you created, or a document that is shared with you from another account.
For SSM documents that are shared with you from other Amazon Web Services accounts, you must specify the complete SSM document ARN, in the following format:
arn:aws:ssm:region:account-id:document/document-name
For example:
arn:aws:ssm:us-east-2:12345678912:document/My-Shared-Document
For Amazon Web Services-predefined documents and SSM documents you created in your account, you only need to specify the document name. For example, AWS-ApplyPatchBaseline
or My-Document
.
Sourcepub fn instance_id(&self) -> Option<&str>
pub fn instance_id(&self) -> Option<&str>
The managed node ID.
InstanceId
has been deprecated. To specify a managed node ID for an association, use the Targets
parameter. Requests that include the parameter InstanceID
with Systems Manager documents (SSM documents) that use schema version 2.0 or later will fail. In addition, if you use the parameter InstanceId
, you can't use the parameters AssociationName
, DocumentVersion
, MaxErrors
, MaxConcurrency
, OutputLocation
, or ScheduleExpression
. To use these parameters, you must use the Targets
parameter.
Sourcepub fn parameters(&self) -> Option<&HashMap<String, Vec<String>>>
pub fn parameters(&self) -> Option<&HashMap<String, Vec<String>>>
A description of the parameters for a document.
Sourcepub fn automation_target_parameter_name(&self) -> Option<&str>
pub fn automation_target_parameter_name(&self) -> Option<&str>
Specify the target for the association. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a tool in Amazon Web Services Systems Manager.
Sourcepub fn document_version(&self) -> Option<&str>
pub fn document_version(&self) -> Option<&str>
The document version.
Sourcepub fn targets(&self) -> &[Target]
pub fn targets(&self) -> &[Target]
The managed nodes targeted by the request.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .targets.is_none()
.
Sourcepub fn schedule_expression(&self) -> Option<&str>
pub fn schedule_expression(&self) -> Option<&str>
A cron expression that specifies a schedule when the association runs.
Sourcepub fn output_location(&self) -> Option<&InstanceAssociationOutputLocation>
pub fn output_location(&self) -> Option<&InstanceAssociationOutputLocation>
An S3 bucket where you want to store the results of this request.
Sourcepub fn association_name(&self) -> Option<&str>
pub fn association_name(&self) -> Option<&str>
Specify a descriptive name for the association.
Sourcepub fn max_errors(&self) -> Option<&str>
pub fn max_errors(&self) -> Option<&str>
The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set MaxError
to 10%, then the system stops sending the request when the sixth error is received.
Executions that are already running an association when MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, set MaxConcurrency
to 1 so that executions proceed one at a time.
Sourcepub fn max_concurrency(&self) -> Option<&str>
pub fn max_concurrency(&self) -> Option<&str>
The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified for MaxConcurrency
.
Sourcepub fn compliance_severity(&self) -> Option<&AssociationComplianceSeverity>
pub fn compliance_severity(&self) -> Option<&AssociationComplianceSeverity>
The severity level to assign to the association.
Sourcepub fn sync_compliance(&self) -> Option<&AssociationSyncCompliance>
pub fn sync_compliance(&self) -> Option<&AssociationSyncCompliance>
The mode for generating association compliance. You can specify AUTO
or MANUAL
. In AUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association is COMPLIANT
. If the association execution doesn't run successfully, the association is NON-COMPLIANT
.
In MANUAL
mode, you must specify the AssociationId
as a parameter for the PutComplianceItems
API operation. In this case, compliance data isn't managed by State Manager, a tool in Amazon Web Services Systems Manager. It is managed by your direct call to the PutComplianceItems
API operation.
By default, all associations use AUTO
mode.
Sourcepub fn apply_only_at_cron_interval(&self) -> bool
pub fn apply_only_at_cron_interval(&self) -> bool
By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified and when target changes are detected. Specify true
for ApplyOnlyAtCronInterval
if you want the association to run only according to the schedule you specified.
For more information, see Understanding when associations are applied to resources and >About target updates with Automation runbooks in the Amazon Web Services Systems Manager User Guide.
This parameter isn't supported for rate expressions.
Sourcepub fn calendar_names(&self) -> &[String]
pub fn calendar_names(&self) -> &[String]
The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see Amazon Web Services Systems Manager Change Calendar in the Amazon Web Services Systems Manager 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 .calendar_names.is_none()
.
Sourcepub fn target_locations(&self) -> &[TargetLocation]
pub fn target_locations(&self) -> &[TargetLocation]
Use this action to create an association in multiple Regions and multiple accounts.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .target_locations.is_none()
.
Sourcepub fn schedule_offset(&self) -> Option<i32>
pub fn schedule_offset(&self) -> Option<i32>
Number of days to wait after the scheduled day to run an association.
Sourcepub fn duration(&self) -> Option<i32>
pub fn duration(&self) -> Option<i32>
The number of hours the association can run before it is canceled. Duration applies to associations that are currently running, and any pending and in progress commands on all targets. If a target was taken offline for the association to run, it is made available again immediately, without a reboot.
The Duration
parameter applies only when both these conditions are true:
-
The association for which you specify a duration is cancelable according to the parameters of the SSM command document or Automation runbook associated with this execution.
-
The command specifies the
ApplyOnlyAtCronInterval
parameter, which means that the association doesn't run immediately after it is created, but only according to the specified schedule.
Sourcepub fn target_maps(&self) -> &[HashMap<String, Vec<String>>]
pub fn target_maps(&self) -> &[HashMap<String, Vec<String>>]
A key-value mapping of document parameters to target resources. Both Targets and TargetMaps can't be specified together.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .target_maps.is_none()
.
Sourcepub fn alarm_configuration(&self) -> Option<&AlarmConfiguration>
pub fn alarm_configuration(&self) -> Option<&AlarmConfiguration>
The details for the CloudWatch alarm you want to apply to an automation or command.
Source§impl CreateAssociationBatchRequestEntry
impl CreateAssociationBatchRequestEntry
Sourcepub fn builder() -> CreateAssociationBatchRequestEntryBuilder
pub fn builder() -> CreateAssociationBatchRequestEntryBuilder
Creates a new builder-style object to manufacture CreateAssociationBatchRequestEntry
.
Trait Implementations§
Source§impl Clone for CreateAssociationBatchRequestEntry
impl Clone for CreateAssociationBatchRequestEntry
Source§fn clone(&self) -> CreateAssociationBatchRequestEntry
fn clone(&self) -> CreateAssociationBatchRequestEntry
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for CreateAssociationBatchRequestEntry
impl PartialEq for CreateAssociationBatchRequestEntry
Source§fn eq(&self, other: &CreateAssociationBatchRequestEntry) -> bool
fn eq(&self, other: &CreateAssociationBatchRequestEntry) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for CreateAssociationBatchRequestEntry
Auto Trait Implementations§
impl Freeze for CreateAssociationBatchRequestEntry
impl RefUnwindSafe for CreateAssociationBatchRequestEntry
impl Send for CreateAssociationBatchRequestEntry
impl Sync for CreateAssociationBatchRequestEntry
impl Unpin for CreateAssociationBatchRequestEntry
impl UnwindSafe for CreateAssociationBatchRequestEntry
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);