#[non_exhaustive]pub struct Compliance {
pub status: Option<ComplianceStatus>,
pub related_requirements: Option<Vec<String>>,
pub status_reasons: Option<Vec<StatusReason>>,
pub security_control_id: Option<String>,
pub associated_standards: Option<Vec<AssociatedStandard>>,
pub security_control_parameters: Option<Vec<SecurityControlParameter>>,
}
Expand description
This object typically provides details about a control finding, such as applicable standards and the status of control checks. While finding providers can add custom content in Compliance
object fields, they are typically used to review details of Security Hub control findings.
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.status: Option<ComplianceStatus>
Typically summarizes the result of a control check.
For Security Hub controls, valid values for Status
are as follows.
-
-
PASSED
- Standards check passed for all evaluated resources. -
WARNING
- Some information is missing or this check is not supported for your configuration. -
FAILED
- Standards check failed for at least one evaluated resource. -
NOT_AVAILABLE
- Check could not be performed due to a service outage, API error, or because the result of the Config evaluation wasNOT_APPLICABLE
. If the Config evaluation result wasNOT_APPLICABLE
for a Security Hub control, Security Hub automatically archives the finding after 3 days.
-
Typically provides the industry or regulatory framework requirements that are related to a control. The check for that control is aligned with these requirements.
Array Members: Maximum number of 32 items.
status_reasons: Option<Vec<StatusReason>>
Typically used to provide a list of reasons for the value of Status
.
security_control_id: Option<String>
Typically provides the unique identifier of a control across standards. For Security Hub controls, this field consists of an Amazon Web Services service and a unique number, such as APIGateway.5
.
associated_standards: Option<Vec<AssociatedStandard>>
Typically provides an array of enabled security standards in which a security control is currently enabled.
security_control_parameters: Option<Vec<SecurityControlParameter>>
Typically an object that includes security control parameter names and values.
Implementations§
Source§impl Compliance
impl Compliance
Sourcepub fn status(&self) -> Option<&ComplianceStatus>
pub fn status(&self) -> Option<&ComplianceStatus>
Typically summarizes the result of a control check.
For Security Hub controls, valid values for Status
are as follows.
-
-
PASSED
- Standards check passed for all evaluated resources. -
WARNING
- Some information is missing or this check is not supported for your configuration. -
FAILED
- Standards check failed for at least one evaluated resource. -
NOT_AVAILABLE
- Check could not be performed due to a service outage, API error, or because the result of the Config evaluation wasNOT_APPLICABLE
. If the Config evaluation result wasNOT_APPLICABLE
for a Security Hub control, Security Hub automatically archives the finding after 3 days.
-
Typically provides the industry or regulatory framework requirements that are related to a control. The check for that control is aligned with these requirements.
Array Members: Maximum number of 32 items.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .related_requirements.is_none()
.
Sourcepub fn status_reasons(&self) -> &[StatusReason]
pub fn status_reasons(&self) -> &[StatusReason]
Typically used to provide a list of reasons for the value of Status
.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .status_reasons.is_none()
.
Sourcepub fn security_control_id(&self) -> Option<&str>
pub fn security_control_id(&self) -> Option<&str>
Typically provides the unique identifier of a control across standards. For Security Hub controls, this field consists of an Amazon Web Services service and a unique number, such as APIGateway.5
.
Sourcepub fn associated_standards(&self) -> &[AssociatedStandard]
pub fn associated_standards(&self) -> &[AssociatedStandard]
Typically provides an array of enabled security standards in which a security control is currently enabled.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .associated_standards.is_none()
.
Sourcepub fn security_control_parameters(&self) -> &[SecurityControlParameter]
pub fn security_control_parameters(&self) -> &[SecurityControlParameter]
Typically an object that includes security control parameter names and values.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .security_control_parameters.is_none()
.
Source§impl Compliance
impl Compliance
Sourcepub fn builder() -> ComplianceBuilder
pub fn builder() -> ComplianceBuilder
Creates a new builder-style object to manufacture Compliance
.
Trait Implementations§
Source§impl Clone for Compliance
impl Clone for Compliance
Source§fn clone(&self) -> Compliance
fn clone(&self) -> Compliance
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for Compliance
impl Debug for Compliance
Source§impl PartialEq for Compliance
impl PartialEq for Compliance
impl StructuralPartialEq for Compliance
Auto Trait Implementations§
impl Freeze for Compliance
impl RefUnwindSafe for Compliance
impl Send for Compliance
impl Sync for Compliance
impl Unpin for Compliance
impl UnwindSafe for Compliance
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);