#[non_exhaustive]pub struct CreateAutomatedReasoningPolicyTestCaseInput {
pub policy_arn: Option<String>,
pub guard_content: Option<String>,
pub query_content: Option<String>,
pub expected_aggregated_findings_result: Option<AutomatedReasoningCheckResult>,
pub client_request_token: Option<String>,
pub confidence_threshold: Option<f64>,
}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.policy_arn: Option<String>The Amazon Resource Name (ARN) of the Automated Reasoning policy for which to create the test.
guard_content: Option<String>The output content that's validated by the Automated Reasoning policy. This represents the foundation model response that will be checked for accuracy.
query_content: Option<String>The input query or prompt that generated the content. This provides context for the validation.
expected_aggregated_findings_result: Option<AutomatedReasoningCheckResult>The expected result of the Automated Reasoning check. Valid values include: , TOO_COMPLEX, and NO_TRANSLATIONS.
-
VALID- The claims are true. The claims are implied by the premises and the Automated Reasoning policy. Given the Automated Reasoning policy and premises, it is not possible for these claims to be false. In other words, there are no alternative answers that are true that contradict the claims. -
INVALID- The claims are false. The claims are not implied by the premises and Automated Reasoning policy. Furthermore, there exists different claims that are consistent with the premises and Automated Reasoning policy. -
SATISFIABLE- The claims can be true or false. It depends on what assumptions are made for the claim to be implied from the premises and Automated Reasoning policy rules. In this situation, different assumptions can make input claims false and alternative claims true. -
IMPOSSIBLE- Automated Reasoning can’t make a statement about the claims. This can happen if the premises are logically incorrect, or if there is a conflict within the Automated Reasoning policy itself. -
TRANSLATION_AMBIGUOUS- Detected an ambiguity in the translation meant it would be unsound to continue with validity checking. Additional context or follow-up questions might be needed to get translation to succeed. -
TOO_COMPLEX- The input contains too much information for Automated Reasoning to process within its latency limits. -
NO_TRANSLATIONS- Identifies that some or all of the input prompt wasn't translated into logic. This can happen if the input isn't relevant to the Automated Reasoning policy, or if the policy doesn't have variables to model relevant input. If Automated Reasoning can't translate anything, you get a singleNO_TRANSLATIONSfinding. You might also see aNO_TRANSLATIONS(along with other findings) if some part of the validation isn't translated.
client_request_token: Option<String>A unique, case-sensitive identifier to ensure that the operation completes no more than one time. If this token matches a previous request, Amazon Bedrock ignores the request, but does not return an error.
confidence_threshold: Option<f64>The minimum confidence level for logic validation. Content that meets the threshold is considered a high-confidence finding that can be validated.
Implementations§
Source§impl CreateAutomatedReasoningPolicyTestCaseInput
impl CreateAutomatedReasoningPolicyTestCaseInput
Sourcepub fn policy_arn(&self) -> Option<&str>
pub fn policy_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the Automated Reasoning policy for which to create the test.
Sourcepub fn guard_content(&self) -> Option<&str>
pub fn guard_content(&self) -> Option<&str>
The output content that's validated by the Automated Reasoning policy. This represents the foundation model response that will be checked for accuracy.
Sourcepub fn query_content(&self) -> Option<&str>
pub fn query_content(&self) -> Option<&str>
The input query or prompt that generated the content. This provides context for the validation.
Sourcepub fn expected_aggregated_findings_result(
&self,
) -> Option<&AutomatedReasoningCheckResult>
pub fn expected_aggregated_findings_result( &self, ) -> Option<&AutomatedReasoningCheckResult>
The expected result of the Automated Reasoning check. Valid values include: , TOO_COMPLEX, and NO_TRANSLATIONS.
-
VALID- The claims are true. The claims are implied by the premises and the Automated Reasoning policy. Given the Automated Reasoning policy and premises, it is not possible for these claims to be false. In other words, there are no alternative answers that are true that contradict the claims. -
INVALID- The claims are false. The claims are not implied by the premises and Automated Reasoning policy. Furthermore, there exists different claims that are consistent with the premises and Automated Reasoning policy. -
SATISFIABLE- The claims can be true or false. It depends on what assumptions are made for the claim to be implied from the premises and Automated Reasoning policy rules. In this situation, different assumptions can make input claims false and alternative claims true. -
IMPOSSIBLE- Automated Reasoning can’t make a statement about the claims. This can happen if the premises are logically incorrect, or if there is a conflict within the Automated Reasoning policy itself. -
TRANSLATION_AMBIGUOUS- Detected an ambiguity in the translation meant it would be unsound to continue with validity checking. Additional context or follow-up questions might be needed to get translation to succeed. -
TOO_COMPLEX- The input contains too much information for Automated Reasoning to process within its latency limits. -
NO_TRANSLATIONS- Identifies that some or all of the input prompt wasn't translated into logic. This can happen if the input isn't relevant to the Automated Reasoning policy, or if the policy doesn't have variables to model relevant input. If Automated Reasoning can't translate anything, you get a singleNO_TRANSLATIONSfinding. You might also see aNO_TRANSLATIONS(along with other findings) if some part of the validation isn't translated.
Sourcepub fn client_request_token(&self) -> Option<&str>
pub fn client_request_token(&self) -> Option<&str>
A unique, case-sensitive identifier to ensure that the operation completes no more than one time. If this token matches a previous request, Amazon Bedrock ignores the request, but does not return an error.
Sourcepub fn confidence_threshold(&self) -> Option<f64>
pub fn confidence_threshold(&self) -> Option<f64>
The minimum confidence level for logic validation. Content that meets the threshold is considered a high-confidence finding that can be validated.
Source§impl CreateAutomatedReasoningPolicyTestCaseInput
impl CreateAutomatedReasoningPolicyTestCaseInput
Sourcepub fn builder() -> CreateAutomatedReasoningPolicyTestCaseInputBuilder
pub fn builder() -> CreateAutomatedReasoningPolicyTestCaseInputBuilder
Creates a new builder-style object to manufacture CreateAutomatedReasoningPolicyTestCaseInput.
Trait Implementations§
Source§impl Clone for CreateAutomatedReasoningPolicyTestCaseInput
impl Clone for CreateAutomatedReasoningPolicyTestCaseInput
Source§fn clone(&self) -> CreateAutomatedReasoningPolicyTestCaseInput
fn clone(&self) -> CreateAutomatedReasoningPolicyTestCaseInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl PartialEq for CreateAutomatedReasoningPolicyTestCaseInput
impl PartialEq for CreateAutomatedReasoningPolicyTestCaseInput
Source§fn eq(&self, other: &CreateAutomatedReasoningPolicyTestCaseInput) -> bool
fn eq(&self, other: &CreateAutomatedReasoningPolicyTestCaseInput) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for CreateAutomatedReasoningPolicyTestCaseInput
Auto Trait Implementations§
impl Freeze for CreateAutomatedReasoningPolicyTestCaseInput
impl RefUnwindSafe for CreateAutomatedReasoningPolicyTestCaseInput
impl Send for CreateAutomatedReasoningPolicyTestCaseInput
impl Sync for CreateAutomatedReasoningPolicyTestCaseInput
impl Unpin for CreateAutomatedReasoningPolicyTestCaseInput
impl UnwindSafe for CreateAutomatedReasoningPolicyTestCaseInput
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);