Struct PutComplianceItemsInput 

#[non_exhaustive]
pub struct PutComplianceItemsInput {
    pub resource_id: Option<String>,
    pub resource_type: Option<String>,
    pub compliance_type: Option<String>,
    pub execution_summary: Option<ComplianceExecutionSummary>,
    pub items: Option<Vec<ComplianceItemEntry>>,
    pub item_content_hash: Option<String>,
    pub upload_type: Option<ComplianceUploadType>,
}

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.

resource_id: Option<String>

Specify an ID for this resource. For a managed node, this is the node ID.

resource_type: Option<String>

Specify the type of resource. ManagedInstance is currently the only supported resource type.

compliance_type: Option<String>

Specify the compliance type. For example, specify Association (for a State Manager association), Patch, or Custom:string.

execution_summary: Option<ComplianceExecutionSummary>

A summary of the call execution that includes an execution ID, the type of execution (for example, Command), and the date/time of the execution using a datetime object that is saved in the following format: yyyy-MM-dd'T'HH:mm:ss'Z'

items: Option<Vec<ComplianceItemEntry>>

Information about the compliance as defined by the resource type. For example, for a patch compliance type, Items includes information about the PatchSeverity, Classification, and so on.

item_content_hash: Option<String>

MD5 or SHA-256 content hash. The content hash is used to determine if existing information should be overwritten or ignored. If the content hashes match, the request to put compliance information is ignored.

upload_type: Option<ComplianceUploadType>

The mode for uploading compliance items. You can specify COMPLETE or PARTIAL. In COMPLETE mode, the system overwrites all existing compliance information for the resource. You must provide a full list of compliance items each time you send the request.

In PARTIAL mode, the system overwrites compliance information for a specific association. The association must be configured with SyncCompliance set to MANUAL. By default, all requests use COMPLETE mode.

This attribute is only valid for association compliance.

Implementations

impl PutComplianceItemsInput

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

Specify an ID for this resource. For a managed node, this is the node ID.

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

Specify the type of resource. ManagedInstance is currently the only supported resource type.

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

Specify the compliance type. For example, specify Association (for a State Manager association), Patch, or Custom:string.

pub fn execution_summary(&self) -> Option<&ComplianceExecutionSummary>

A summary of the call execution that includes an execution ID, the type of execution (for example, Command), and the date/time of the execution using a datetime object that is saved in the following format: yyyy-MM-dd'T'HH:mm:ss'Z'

pub fn items(&self) -> &[ComplianceItemEntry]

Information about the compliance as defined by the resource type. For example, for a patch compliance type, Items includes information about the PatchSeverity, Classification, and so on.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .items.is_none().

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

MD5 or SHA-256 content hash. The content hash is used to determine if existing information should be overwritten or ignored. If the content hashes match, the request to put compliance information is ignored.

pub fn upload_type(&self) -> Option<&ComplianceUploadType>

The mode for uploading compliance items. You can specify COMPLETE or PARTIAL. In COMPLETE mode, the system overwrites all existing compliance information for the resource. You must provide a full list of compliance items each time you send the request.

In PARTIAL mode, the system overwrites compliance information for a specific association. The association must be configured with SyncCompliance set to MANUAL. By default, all requests use COMPLETE mode.

This attribute is only valid for association compliance.

impl PutComplianceItemsInput

pub fn builder() -> PutComplianceItemsInputBuilder

Creates a new builder-style object to manufacture PutComplianceItemsInput.

Trait Implementations

impl Clone for PutComplianceItemsInput

fn clone(&self) -> PutComplianceItemsInput

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for PutComplianceItemsInput

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

Formats the value using the given formatter.

impl PartialEq for PutComplianceItemsInput

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

Tests for self and other values to be equal, and is used by ==.

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

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for PutComplianceItemsInput