#[non_exhaustive]pub struct CreatePatchBaselineInput {Show 14 fields
pub operating_system: Option<OperatingSystem>,
pub name: Option<String>,
pub global_filters: Option<PatchFilterGroup>,
pub approval_rules: Option<PatchRuleGroup>,
pub approved_patches: Option<Vec<String>>,
pub approved_patches_compliance_level: Option<PatchComplianceLevel>,
pub approved_patches_enable_non_security: Option<bool>,
pub rejected_patches: Option<Vec<String>>,
pub rejected_patches_action: Option<PatchAction>,
pub description: Option<String>,
pub sources: Option<Vec<PatchSource>>,
pub available_security_updates_compliance_status: Option<PatchComplianceStatus>,
pub client_token: Option<String>,
pub tags: Option<Vec<Tag>>,
}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.operating_system: Option<OperatingSystem>Defines the operating system the patch baseline applies to. The default value is WINDOWS.
name: Option<String>The name of the patch baseline.
global_filters: Option<PatchFilterGroup>A set of global filters used to include patches in the baseline.
The GlobalFilters parameter can be configured only by using the CLI or an Amazon Web Services SDK. It can't be configured from the Patch Manager console, and its value isn't displayed in the console.
approval_rules: Option<PatchRuleGroup>A set of rules used to include patches in the baseline.
approved_patches: Option<Vec<String>>A list of explicitly approved patches for the baseline.
For information about accepted formats for lists of approved patches and rejected patches, see Package name formats for approved and rejected patch lists in the Amazon Web Services Systems Manager User Guide.
approved_patches_compliance_level: Option<PatchComplianceLevel>Defines the compliance level for approved patches. When an approved patch is reported as missing, this value describes the severity of the compliance violation. The default value is UNSPECIFIED.
approved_patches_enable_non_security: Option<bool>Indicates whether the list of approved patches includes non-security updates that should be applied to the managed nodes. The default value is false. Applies to Linux managed nodes only.
rejected_patches: Option<Vec<String>>A list of explicitly rejected patches for the baseline.
For information about accepted formats for lists of approved patches and rejected patches, see Package name formats for approved and rejected patch lists in the Amazon Web Services Systems Manager User Guide.
rejected_patches_action: Option<PatchAction>The action for Patch Manager to take on patches included in the RejectedPackages list.
- ALLOW_AS_DEPENDENCY
-
Linux and macOS: A package in the rejected patches list is installed only if it is a dependency of another package. It is considered compliant with the patch baseline, and its status is reported as
INSTALLED_OTHER. This is the default action if no option is specified.Windows Server: Windows Server doesn't support the concept of package dependencies. If a package in the rejected patches list and already installed on the node, its status is reported as
INSTALLED_OTHER. Any package not already installed on the node is skipped. This is the default action if no option is specified. - BLOCK
-
All OSs: Packages in the rejected patches list, and packages that include them as dependencies, aren't installed by Patch Manager under any circumstances. If a package was installed before it was added to the rejected patches list, or is installed outside of Patch Manager afterward, it's considered noncompliant with the patch baseline and its status is reported as
INSTALLED_REJECTED.
description: Option<String>A description of the patch baseline.
sources: Option<Vec<PatchSource>>Information about the patches to use to update the managed nodes, including target operating systems and source repositories. Applies to Linux managed nodes only.
available_security_updates_compliance_status: Option<PatchComplianceStatus>Indicates the status you want to assign to security patches that are available but not approved because they don't meet the installation criteria specified in the patch baseline.
Example scenario: Security patches that you might want installed can be skipped if you have specified a long period to wait after a patch is released before installation. If an update to the patch is released during your specified waiting period, the waiting period for installing the patch starts over. If the waiting period is too long, multiple versions of the patch could be released but never installed.
Supported for Windows Server managed nodes only.
client_token: Option<String>User-provided idempotency token.
Optional metadata that you assign to a resource. Tags enable you to categorize a resource in different ways, such as by purpose, owner, or environment. For example, you might want to tag a patch baseline to identify the severity level of patches it specifies and the operating system family it applies to. In this case, you could specify the following key-value pairs:
-
Key=PatchSeverity,Value=Critical -
Key=OS,Value=Windows
To add tags to an existing patch baseline, use the AddTagsToResource operation.
Implementations§
Source§impl CreatePatchBaselineInput
impl CreatePatchBaselineInput
Sourcepub fn operating_system(&self) -> Option<&OperatingSystem>
pub fn operating_system(&self) -> Option<&OperatingSystem>
Defines the operating system the patch baseline applies to. The default value is WINDOWS.
Sourcepub fn global_filters(&self) -> Option<&PatchFilterGroup>
pub fn global_filters(&self) -> Option<&PatchFilterGroup>
A set of global filters used to include patches in the baseline.
The GlobalFilters parameter can be configured only by using the CLI or an Amazon Web Services SDK. It can't be configured from the Patch Manager console, and its value isn't displayed in the console.
Sourcepub fn approval_rules(&self) -> Option<&PatchRuleGroup>
pub fn approval_rules(&self) -> Option<&PatchRuleGroup>
A set of rules used to include patches in the baseline.
Sourcepub fn approved_patches(&self) -> &[String]
pub fn approved_patches(&self) -> &[String]
A list of explicitly approved patches for the baseline.
For information about accepted formats for lists of approved patches and rejected patches, see Package name formats for approved and rejected patch lists 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 .approved_patches.is_none().
Sourcepub fn approved_patches_compliance_level(&self) -> Option<&PatchComplianceLevel>
pub fn approved_patches_compliance_level(&self) -> Option<&PatchComplianceLevel>
Defines the compliance level for approved patches. When an approved patch is reported as missing, this value describes the severity of the compliance violation. The default value is UNSPECIFIED.
Sourcepub fn approved_patches_enable_non_security(&self) -> Option<bool>
pub fn approved_patches_enable_non_security(&self) -> Option<bool>
Indicates whether the list of approved patches includes non-security updates that should be applied to the managed nodes. The default value is false. Applies to Linux managed nodes only.
Sourcepub fn rejected_patches(&self) -> &[String]
pub fn rejected_patches(&self) -> &[String]
A list of explicitly rejected patches for the baseline.
For information about accepted formats for lists of approved patches and rejected patches, see Package name formats for approved and rejected patch lists 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 .rejected_patches.is_none().
Sourcepub fn rejected_patches_action(&self) -> Option<&PatchAction>
pub fn rejected_patches_action(&self) -> Option<&PatchAction>
The action for Patch Manager to take on patches included in the RejectedPackages list.
- ALLOW_AS_DEPENDENCY
-
Linux and macOS: A package in the rejected patches list is installed only if it is a dependency of another package. It is considered compliant with the patch baseline, and its status is reported as
INSTALLED_OTHER. This is the default action if no option is specified.Windows Server: Windows Server doesn't support the concept of package dependencies. If a package in the rejected patches list and already installed on the node, its status is reported as
INSTALLED_OTHER. Any package not already installed on the node is skipped. This is the default action if no option is specified. - BLOCK
-
All OSs: Packages in the rejected patches list, and packages that include them as dependencies, aren't installed by Patch Manager under any circumstances. If a package was installed before it was added to the rejected patches list, or is installed outside of Patch Manager afterward, it's considered noncompliant with the patch baseline and its status is reported as
INSTALLED_REJECTED.
Sourcepub fn description(&self) -> Option<&str>
pub fn description(&self) -> Option<&str>
A description of the patch baseline.
Sourcepub fn sources(&self) -> &[PatchSource]
pub fn sources(&self) -> &[PatchSource]
Information about the patches to use to update the managed nodes, including target operating systems and source repositories. Applies to Linux managed nodes only.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .sources.is_none().
Sourcepub fn available_security_updates_compliance_status(
&self,
) -> Option<&PatchComplianceStatus>
pub fn available_security_updates_compliance_status( &self, ) -> Option<&PatchComplianceStatus>
Indicates the status you want to assign to security patches that are available but not approved because they don't meet the installation criteria specified in the patch baseline.
Example scenario: Security patches that you might want installed can be skipped if you have specified a long period to wait after a patch is released before installation. If an update to the patch is released during your specified waiting period, the waiting period for installing the patch starts over. If the waiting period is too long, multiple versions of the patch could be released but never installed.
Supported for Windows Server managed nodes only.
Sourcepub fn client_token(&self) -> Option<&str>
pub fn client_token(&self) -> Option<&str>
User-provided idempotency token.
Optional metadata that you assign to a resource. Tags enable you to categorize a resource in different ways, such as by purpose, owner, or environment. For example, you might want to tag a patch baseline to identify the severity level of patches it specifies and the operating system family it applies to. In this case, you could specify the following key-value pairs:
-
Key=PatchSeverity,Value=Critical -
Key=OS,Value=Windows
To add tags to an existing patch baseline, use the AddTagsToResource operation.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .tags.is_none().
Source§impl CreatePatchBaselineInput
impl CreatePatchBaselineInput
Sourcepub fn builder() -> CreatePatchBaselineInputBuilder
pub fn builder() -> CreatePatchBaselineInputBuilder
Creates a new builder-style object to manufacture CreatePatchBaselineInput.
Trait Implementations§
Source§impl Clone for CreatePatchBaselineInput
impl Clone for CreatePatchBaselineInput
Source§fn clone(&self) -> CreatePatchBaselineInput
fn clone(&self) -> CreatePatchBaselineInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for CreatePatchBaselineInput
impl Debug for CreatePatchBaselineInput
Source§impl PartialEq for CreatePatchBaselineInput
impl PartialEq for CreatePatchBaselineInput
impl StructuralPartialEq for CreatePatchBaselineInput
Auto Trait Implementations§
impl Freeze for CreatePatchBaselineInput
impl RefUnwindSafe for CreatePatchBaselineInput
impl Send for CreatePatchBaselineInput
impl Sync for CreatePatchBaselineInput
impl Unpin for CreatePatchBaselineInput
impl UnwindSafe for CreatePatchBaselineInput
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);