[][src]Struct rusoto_ssm::AssociationVersionInfo

pub struct AssociationVersionInfo {
    pub apply_only_at_cron_interval: Option<bool>,
    pub association_id: Option<String>,
    pub association_name: Option<String>,
    pub association_version: Option<String>,
    pub compliance_severity: Option<String>,
    pub created_date: Option<f64>,
    pub document_version: Option<String>,
    pub max_concurrency: Option<String>,
    pub max_errors: Option<String>,
    pub name: Option<String>,
    pub output_location: Option<InstanceAssociationOutputLocation>,
    pub parameters: Option<HashMap<String, Vec<String>>>,
    pub schedule_expression: Option<String>,
    pub sync_compliance: Option<String>,
    pub targets: Option<Vec<Target>>,
}

Information about the association version.

Fields

apply_only_at_cron_interval: Option<bool>

By default, when you create a new associations, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you create it.

association_id: Option<String>

The ID created by the system when the association was created.

association_name: Option<String>

The name specified for the association version when the association version was created.

association_version: Option<String>

The association version.

compliance_severity: Option<String>

The severity level that is assigned to the association.

created_date: Option<f64>

The date the association version was created.

document_version: Option<String>

The version of a Systems Manager document used when the association version was created.

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 instance 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 instance will process its association within the limit specified for MaxConcurrency.

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 instances 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.

name: Option<String>

The name specified when the association was created.

output_location: Option<InstanceAssociationOutputLocation>

The location in Amazon S3 specified for the association when the association version was created.

parameters: Option<HashMap<String, Vec<String>>>

Parameters specified when the association version was created.

schedule_expression: Option<String>

The cron or rate schedule specified for the association when the association version was created.

sync_compliance: Option<String>

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 action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to the PutComplianceItems API action.

By default, all associations use AUTO mode.

targets: Option<Vec<Target>>

The targets specified for the association when the association version was created.

Trait Implementations

impl Clone for AssociationVersionInfo[src]

impl Debug for AssociationVersionInfo[src]

impl Default for AssociationVersionInfo[src]

impl<'de> Deserialize<'de> for AssociationVersionInfo[src]

impl PartialEq<AssociationVersionInfo> for AssociationVersionInfo[src]

impl StructuralPartialEq for AssociationVersionInfo[src]

Auto Trait Implementations

Blanket Implementations

impl<T> Any for T where
    T: 'static + ?Sized
[src]

impl<T> Borrow<T> for T where
    T: ?Sized
[src]

impl<T> BorrowMut<T> for T where
    T: ?Sized
[src]

impl<T> DeserializeOwned for T where
    T: for<'de> Deserialize<'de>, 
[src]

impl<T> From<T> for T[src]

impl<T> Instrument for T[src]

impl<T> Instrument for T[src]

impl<T, U> Into<U> for T where
    U: From<T>, 
[src]

impl<T> Same<T> for T

type Output = T

Should always be Self

impl<T> ToOwned for T where
    T: Clone
[src]

type Owned = T

The resulting type after obtaining ownership.

impl<T, U> TryFrom<U> for T where
    U: Into<T>, 
[src]

type Error = Infallible

The type returned in the event of a conversion error.

impl<T, U> TryInto<U> for T where
    U: TryFrom<T>, 
[src]

type Error = <U as TryFrom<T>>::Error

The type returned in the event of a conversion error.