#[non_exhaustive]pub struct EvaluationResult {
pub eval_action_name: String,
pub eval_resource_name: Option<String>,
pub eval_decision: PolicyEvaluationDecisionType,
pub matched_statements: Option<Vec<Statement>>,
pub missing_context_values: Option<Vec<String>>,
pub organizations_decision_detail: Option<OrganizationsDecisionDetail>,
pub permissions_boundary_decision_detail: Option<PermissionsBoundaryDecisionDetail>,
pub eval_decision_details: Option<HashMap<String, PolicyEvaluationDecisionType>>,
pub resource_specific_results: Option<Vec<ResourceSpecificResult>>,
}
Expand description
Contains the results of a simulation.
This data type is used by the return parameter of SimulateCustomPolicy
and SimulatePrincipalPolicy
.
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.eval_action_name: String
The name of the API operation tested on the indicated resource.
eval_resource_name: Option<String>
The ARN of the resource that the indicated API operation was tested on.
eval_decision: PolicyEvaluationDecisionType
The result of the simulation.
matched_statements: Option<Vec<Statement>>
A list of the statements in the input policies that determine the result for this scenario. Remember that even if multiple statements allow the operation on the resource, if only one statement denies that operation, then the explicit deny overrides any allow. In addition, the deny statement is the only entry included in the result.
missing_context_values: Option<Vec<String>>
A list of context keys that are required by the included input policies but that were not provided by one of the input parameters. This list is used when the resource in a simulation is "*", either explicitly, or when the ResourceArns
parameter blank. If you include a list of resources, then any missing context values are instead included under the ResourceSpecificResults
section. To discover the context keys used by a set of policies, you can call GetContextKeysForCustomPolicy or GetContextKeysForPrincipalPolicy.
organizations_decision_detail: Option<OrganizationsDecisionDetail>
A structure that details how Organizations and its service control policies affect the results of the simulation. Only applies if the simulated user's account is part of an organization.
permissions_boundary_decision_detail: Option<PermissionsBoundaryDecisionDetail>
Contains information about the effect that a permissions boundary has on a policy simulation when the boundary is applied to an IAM entity.
eval_decision_details: Option<HashMap<String, PolicyEvaluationDecisionType>>
Additional details about the results of the cross-account evaluation decision. This parameter is populated for only cross-account simulations. It contains a brief summary of how each policy type contributes to the final evaluation decision.
If the simulation evaluates policies within the same account and includes a resource ARN, then the parameter is present but the response is empty. If the simulation evaluates policies within the same account and specifies all resources (*
), then the parameter is not returned.
When you make a cross-account request, Amazon Web Services evaluates the request in the trusting account and the trusted account. The request is allowed only if both evaluations return true
. For more information about how policies are evaluated, see Evaluating policies within a single account.
If an Organizations SCP included in the evaluation denies access, the simulation ends. In this case, policy evaluation does not proceed any further and this parameter is not returned.
resource_specific_results: Option<Vec<ResourceSpecificResult>>
The individual results of the simulation of the API operation specified in EvalActionName on each resource.
Implementations§
Source§impl EvaluationResult
impl EvaluationResult
Sourcepub fn eval_action_name(&self) -> &str
pub fn eval_action_name(&self) -> &str
The name of the API operation tested on the indicated resource.
Sourcepub fn eval_resource_name(&self) -> Option<&str>
pub fn eval_resource_name(&self) -> Option<&str>
The ARN of the resource that the indicated API operation was tested on.
Sourcepub fn eval_decision(&self) -> &PolicyEvaluationDecisionType
pub fn eval_decision(&self) -> &PolicyEvaluationDecisionType
The result of the simulation.
Sourcepub fn matched_statements(&self) -> &[Statement]
pub fn matched_statements(&self) -> &[Statement]
A list of the statements in the input policies that determine the result for this scenario. Remember that even if multiple statements allow the operation on the resource, if only one statement denies that operation, then the explicit deny overrides any allow. In addition, the deny statement is the only entry included in the result.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .matched_statements.is_none()
.
Sourcepub fn missing_context_values(&self) -> &[String]
pub fn missing_context_values(&self) -> &[String]
A list of context keys that are required by the included input policies but that were not provided by one of the input parameters. This list is used when the resource in a simulation is "*", either explicitly, or when the ResourceArns
parameter blank. If you include a list of resources, then any missing context values are instead included under the ResourceSpecificResults
section. To discover the context keys used by a set of policies, you can call GetContextKeysForCustomPolicy or GetContextKeysForPrincipalPolicy.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .missing_context_values.is_none()
.
Sourcepub fn organizations_decision_detail(
&self,
) -> Option<&OrganizationsDecisionDetail>
pub fn organizations_decision_detail( &self, ) -> Option<&OrganizationsDecisionDetail>
A structure that details how Organizations and its service control policies affect the results of the simulation. Only applies if the simulated user's account is part of an organization.
Sourcepub fn permissions_boundary_decision_detail(
&self,
) -> Option<&PermissionsBoundaryDecisionDetail>
pub fn permissions_boundary_decision_detail( &self, ) -> Option<&PermissionsBoundaryDecisionDetail>
Contains information about the effect that a permissions boundary has on a policy simulation when the boundary is applied to an IAM entity.
Sourcepub fn eval_decision_details(
&self,
) -> Option<&HashMap<String, PolicyEvaluationDecisionType>>
pub fn eval_decision_details( &self, ) -> Option<&HashMap<String, PolicyEvaluationDecisionType>>
Additional details about the results of the cross-account evaluation decision. This parameter is populated for only cross-account simulations. It contains a brief summary of how each policy type contributes to the final evaluation decision.
If the simulation evaluates policies within the same account and includes a resource ARN, then the parameter is present but the response is empty. If the simulation evaluates policies within the same account and specifies all resources (*
), then the parameter is not returned.
When you make a cross-account request, Amazon Web Services evaluates the request in the trusting account and the trusted account. The request is allowed only if both evaluations return true
. For more information about how policies are evaluated, see Evaluating policies within a single account.
If an Organizations SCP included in the evaluation denies access, the simulation ends. In this case, policy evaluation does not proceed any further and this parameter is not returned.
Sourcepub fn resource_specific_results(&self) -> &[ResourceSpecificResult]
pub fn resource_specific_results(&self) -> &[ResourceSpecificResult]
The individual results of the simulation of the API operation specified in EvalActionName on each resource.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .resource_specific_results.is_none()
.
Source§impl EvaluationResult
impl EvaluationResult
Sourcepub fn builder() -> EvaluationResultBuilder
pub fn builder() -> EvaluationResultBuilder
Creates a new builder-style object to manufacture EvaluationResult
.
Trait Implementations§
Source§impl Clone for EvaluationResult
impl Clone for EvaluationResult
Source§fn clone(&self) -> EvaluationResult
fn clone(&self) -> EvaluationResult
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for EvaluationResult
impl Debug for EvaluationResult
Source§impl PartialEq for EvaluationResult
impl PartialEq for EvaluationResult
impl StructuralPartialEq for EvaluationResult
Auto Trait Implementations§
impl Freeze for EvaluationResult
impl RefUnwindSafe for EvaluationResult
impl Send for EvaluationResult
impl Sync for EvaluationResult
impl Unpin for EvaluationResult
impl UnwindSafe for EvaluationResult
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);