#[non_exhaustive]pub struct AdminInitiateAuthOutputBuilder { /* private fields */ }Expand description
A builder for AdminInitiateAuthOutput.
Implementations§
Source§impl AdminInitiateAuthOutputBuilder
impl AdminInitiateAuthOutputBuilder
Sourcepub fn challenge_name(self, input: ChallengeNameType) -> Self
pub fn challenge_name(self, input: ChallengeNameType) -> Self
The name of the challenge that you're responding to with this call. This is returned in the AdminInitiateAuth response if you must pass another challenge.
Possible challenges include the following:
All of the following challenges require USERNAME and, when the app client has a client secret, SECRET_HASH in the parameters. Include a DEVICE_KEY for device authentication.
-
WEB_AUTHN: Respond to the challenge with the results of a successful authentication with a WebAuthn authenticator, or passkey, asCREDENTIAL. Examples of WebAuthn authenticators include biometric devices and security keys. -
PASSWORD: Respond with the user's password asPASSWORD. -
PASSWORD_SRP: Respond with the initial SRP secret asSRP_A. -
SELECT_CHALLENGE: Respond with a challenge selection asANSWER. It must be one of the challenge types in theAvailableChallengesresponse parameter. Add the parameters of the selected challenge, for exampleUSERNAMEandSMS_OTP. -
SMS_MFA: Respond with the code that your user pool delivered in an SMS message, asSMS_MFA_CODE -
EMAIL_MFA: Respond with the code that your user pool delivered in an email message, asEMAIL_MFA_CODE -
EMAIL_OTP: Respond with the code that your user pool delivered in an email message, asEMAIL_OTP_CODE. -
SMS_OTP: Respond with the code that your user pool delivered in an SMS message, asSMS_OTP_CODE. -
PASSWORD_VERIFIER: Respond with the second stage of SRP secrets asPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMP. -
CUSTOM_CHALLENGE: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued. The parameters of the challenge are determined by your Lambda function and issued in theChallengeParametersof a challenge response. -
DEVICE_SRP_AUTH: Respond with the initial parameters of device SRP authentication. For more information, see Signing in with a device. -
DEVICE_PASSWORD_VERIFIER: Respond withPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMPafter client-side SRP calculations. For more information, see Signing in with a device. -
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first login. Respond to this challenge withNEW_PASSWORDand any required attributes that Amazon Cognito returned in therequiredAttributesparameter. You can also set values for attributes that aren't required by your user pool and that your app client can write.Amazon Cognito only returns this challenge for users who have temporary passwords. When you create passwordless users, you must provide values for all required attributes.
In a
NEW_PASSWORD_REQUIREDchallenge response, you can't modify a required attribute that already has a value. InAdminRespondToAuthChallengeorRespondToAuthChallenge, set a value for any keys that Amazon Cognito returned in therequiredAttributesparameter, then use theAdminUpdateUserAttributesorUpdateUserAttributesAPI operation to modify the value of any additional attributes. -
MFA_SETUP: For users who are required to setup an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parametersMFAS_CAN_SETUPvalue.To set up time-based one-time password (TOTP) MFA, use the session returned in this challenge from
InitiateAuthorAdminInitiateAuthas an input toAssociateSoftwareToken. Then, use the session returned byVerifySoftwareTokenas an input toRespondToAuthChallengeorAdminRespondToAuthChallengewith challenge nameMFA_SETUPto complete sign-in.To set up SMS or email MFA, collect a
phone_numberoremailattribute for the user. Then restart the authentication flow with anInitiateAuthorAdminInitiateAuthrequest.
Sourcepub fn set_challenge_name(self, input: Option<ChallengeNameType>) -> Self
pub fn set_challenge_name(self, input: Option<ChallengeNameType>) -> Self
The name of the challenge that you're responding to with this call. This is returned in the AdminInitiateAuth response if you must pass another challenge.
Possible challenges include the following:
All of the following challenges require USERNAME and, when the app client has a client secret, SECRET_HASH in the parameters. Include a DEVICE_KEY for device authentication.
-
WEB_AUTHN: Respond to the challenge with the results of a successful authentication with a WebAuthn authenticator, or passkey, asCREDENTIAL. Examples of WebAuthn authenticators include biometric devices and security keys. -
PASSWORD: Respond with the user's password asPASSWORD. -
PASSWORD_SRP: Respond with the initial SRP secret asSRP_A. -
SELECT_CHALLENGE: Respond with a challenge selection asANSWER. It must be one of the challenge types in theAvailableChallengesresponse parameter. Add the parameters of the selected challenge, for exampleUSERNAMEandSMS_OTP. -
SMS_MFA: Respond with the code that your user pool delivered in an SMS message, asSMS_MFA_CODE -
EMAIL_MFA: Respond with the code that your user pool delivered in an email message, asEMAIL_MFA_CODE -
EMAIL_OTP: Respond with the code that your user pool delivered in an email message, asEMAIL_OTP_CODE. -
SMS_OTP: Respond with the code that your user pool delivered in an SMS message, asSMS_OTP_CODE. -
PASSWORD_VERIFIER: Respond with the second stage of SRP secrets asPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMP. -
CUSTOM_CHALLENGE: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued. The parameters of the challenge are determined by your Lambda function and issued in theChallengeParametersof a challenge response. -
DEVICE_SRP_AUTH: Respond with the initial parameters of device SRP authentication. For more information, see Signing in with a device. -
DEVICE_PASSWORD_VERIFIER: Respond withPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMPafter client-side SRP calculations. For more information, see Signing in with a device. -
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first login. Respond to this challenge withNEW_PASSWORDand any required attributes that Amazon Cognito returned in therequiredAttributesparameter. You can also set values for attributes that aren't required by your user pool and that your app client can write.Amazon Cognito only returns this challenge for users who have temporary passwords. When you create passwordless users, you must provide values for all required attributes.
In a
NEW_PASSWORD_REQUIREDchallenge response, you can't modify a required attribute that already has a value. InAdminRespondToAuthChallengeorRespondToAuthChallenge, set a value for any keys that Amazon Cognito returned in therequiredAttributesparameter, then use theAdminUpdateUserAttributesorUpdateUserAttributesAPI operation to modify the value of any additional attributes. -
MFA_SETUP: For users who are required to setup an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parametersMFAS_CAN_SETUPvalue.To set up time-based one-time password (TOTP) MFA, use the session returned in this challenge from
InitiateAuthorAdminInitiateAuthas an input toAssociateSoftwareToken. Then, use the session returned byVerifySoftwareTokenas an input toRespondToAuthChallengeorAdminRespondToAuthChallengewith challenge nameMFA_SETUPto complete sign-in.To set up SMS or email MFA, collect a
phone_numberoremailattribute for the user. Then restart the authentication flow with anInitiateAuthorAdminInitiateAuthrequest.
Sourcepub fn get_challenge_name(&self) -> &Option<ChallengeNameType>
pub fn get_challenge_name(&self) -> &Option<ChallengeNameType>
The name of the challenge that you're responding to with this call. This is returned in the AdminInitiateAuth response if you must pass another challenge.
Possible challenges include the following:
All of the following challenges require USERNAME and, when the app client has a client secret, SECRET_HASH in the parameters. Include a DEVICE_KEY for device authentication.
-
WEB_AUTHN: Respond to the challenge with the results of a successful authentication with a WebAuthn authenticator, or passkey, asCREDENTIAL. Examples of WebAuthn authenticators include biometric devices and security keys. -
PASSWORD: Respond with the user's password asPASSWORD. -
PASSWORD_SRP: Respond with the initial SRP secret asSRP_A. -
SELECT_CHALLENGE: Respond with a challenge selection asANSWER. It must be one of the challenge types in theAvailableChallengesresponse parameter. Add the parameters of the selected challenge, for exampleUSERNAMEandSMS_OTP. -
SMS_MFA: Respond with the code that your user pool delivered in an SMS message, asSMS_MFA_CODE -
EMAIL_MFA: Respond with the code that your user pool delivered in an email message, asEMAIL_MFA_CODE -
EMAIL_OTP: Respond with the code that your user pool delivered in an email message, asEMAIL_OTP_CODE. -
SMS_OTP: Respond with the code that your user pool delivered in an SMS message, asSMS_OTP_CODE. -
PASSWORD_VERIFIER: Respond with the second stage of SRP secrets asPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMP. -
CUSTOM_CHALLENGE: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued. The parameters of the challenge are determined by your Lambda function and issued in theChallengeParametersof a challenge response. -
DEVICE_SRP_AUTH: Respond with the initial parameters of device SRP authentication. For more information, see Signing in with a device. -
DEVICE_PASSWORD_VERIFIER: Respond withPASSWORD_CLAIM_SIGNATURE,PASSWORD_CLAIM_SECRET_BLOCK, andTIMESTAMPafter client-side SRP calculations. For more information, see Signing in with a device. -
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first login. Respond to this challenge withNEW_PASSWORDand any required attributes that Amazon Cognito returned in therequiredAttributesparameter. You can also set values for attributes that aren't required by your user pool and that your app client can write.Amazon Cognito only returns this challenge for users who have temporary passwords. When you create passwordless users, you must provide values for all required attributes.
In a
NEW_PASSWORD_REQUIREDchallenge response, you can't modify a required attribute that already has a value. InAdminRespondToAuthChallengeorRespondToAuthChallenge, set a value for any keys that Amazon Cognito returned in therequiredAttributesparameter, then use theAdminUpdateUserAttributesorUpdateUserAttributesAPI operation to modify the value of any additional attributes. -
MFA_SETUP: For users who are required to setup an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parametersMFAS_CAN_SETUPvalue.To set up time-based one-time password (TOTP) MFA, use the session returned in this challenge from
InitiateAuthorAdminInitiateAuthas an input toAssociateSoftwareToken. Then, use the session returned byVerifySoftwareTokenas an input toRespondToAuthChallengeorAdminRespondToAuthChallengewith challenge nameMFA_SETUPto complete sign-in.To set up SMS or email MFA, collect a
phone_numberoremailattribute for the user. Then restart the authentication flow with anInitiateAuthorAdminInitiateAuthrequest.
Sourcepub fn session(self, input: impl Into<String>) -> Self
pub fn session(self, input: impl Into<String>) -> Self
The session that must be passed to challenge-response requests. If an AdminInitiateAuth or AdminRespondToAuthChallenge API request results in another authentication challenge, Amazon Cognito returns a session ID and the parameters of the next challenge. Pass this session ID in the Session parameter of AdminRespondToAuthChallenge.
Sourcepub fn set_session(self, input: Option<String>) -> Self
pub fn set_session(self, input: Option<String>) -> Self
The session that must be passed to challenge-response requests. If an AdminInitiateAuth or AdminRespondToAuthChallenge API request results in another authentication challenge, Amazon Cognito returns a session ID and the parameters of the next challenge. Pass this session ID in the Session parameter of AdminRespondToAuthChallenge.
Sourcepub fn get_session(&self) -> &Option<String>
pub fn get_session(&self) -> &Option<String>
The session that must be passed to challenge-response requests. If an AdminInitiateAuth or AdminRespondToAuthChallenge API request results in another authentication challenge, Amazon Cognito returns a session ID and the parameters of the next challenge. Pass this session ID in the Session parameter of AdminRespondToAuthChallenge.
Sourcepub fn challenge_parameters(
self,
k: impl Into<String>,
v: impl Into<String>,
) -> Self
pub fn challenge_parameters( self, k: impl Into<String>, v: impl Into<String>, ) -> Self
Adds a key-value pair to challenge_parameters.
To override the contents of this collection use set_challenge_parameters.
The parameters of an authentication challenge. Amazon Cognito returns challenge parameters as a guide to the responses your user or application must provide for the returned ChallengeName. Calculate responses to the challenge parameters and pass them in the ChallengeParameters of AdminRespondToAuthChallenge.
All challenges require USERNAME and, when the app client has a client secret, SECRET_HASH.
In SRP challenges, Amazon Cognito returns the username attribute in USER_ID_FOR_SRP instead of any email address, preferred username, or phone number alias that you might have specified in your AdminInitiateAuth request. You must use the username and not an alias in the ChallengeResponses of your challenge response.
Sourcepub fn set_challenge_parameters(
self,
input: Option<HashMap<String, String>>,
) -> Self
pub fn set_challenge_parameters( self, input: Option<HashMap<String, String>>, ) -> Self
The parameters of an authentication challenge. Amazon Cognito returns challenge parameters as a guide to the responses your user or application must provide for the returned ChallengeName. Calculate responses to the challenge parameters and pass them in the ChallengeParameters of AdminRespondToAuthChallenge.
All challenges require USERNAME and, when the app client has a client secret, SECRET_HASH.
In SRP challenges, Amazon Cognito returns the username attribute in USER_ID_FOR_SRP instead of any email address, preferred username, or phone number alias that you might have specified in your AdminInitiateAuth request. You must use the username and not an alias in the ChallengeResponses of your challenge response.
Sourcepub fn get_challenge_parameters(&self) -> &Option<HashMap<String, String>>
pub fn get_challenge_parameters(&self) -> &Option<HashMap<String, String>>
The parameters of an authentication challenge. Amazon Cognito returns challenge parameters as a guide to the responses your user or application must provide for the returned ChallengeName. Calculate responses to the challenge parameters and pass them in the ChallengeParameters of AdminRespondToAuthChallenge.
All challenges require USERNAME and, when the app client has a client secret, SECRET_HASH.
In SRP challenges, Amazon Cognito returns the username attribute in USER_ID_FOR_SRP instead of any email address, preferred username, or phone number alias that you might have specified in your AdminInitiateAuth request. You must use the username and not an alias in the ChallengeResponses of your challenge response.
Sourcepub fn authentication_result(self, input: AuthenticationResultType) -> Self
pub fn authentication_result(self, input: AuthenticationResultType) -> Self
The outcome of successful authentication. This is only returned if the user pool has no additional challenges to return. If Amazon Cognito returns another challenge, the response includes ChallengeName, ChallengeParameters, and Session so that your user can answer the challenge.
Sourcepub fn set_authentication_result(
self,
input: Option<AuthenticationResultType>,
) -> Self
pub fn set_authentication_result( self, input: Option<AuthenticationResultType>, ) -> Self
The outcome of successful authentication. This is only returned if the user pool has no additional challenges to return. If Amazon Cognito returns another challenge, the response includes ChallengeName, ChallengeParameters, and Session so that your user can answer the challenge.
Sourcepub fn get_authentication_result(&self) -> &Option<AuthenticationResultType>
pub fn get_authentication_result(&self) -> &Option<AuthenticationResultType>
The outcome of successful authentication. This is only returned if the user pool has no additional challenges to return. If Amazon Cognito returns another challenge, the response includes ChallengeName, ChallengeParameters, and Session so that your user can answer the challenge.
Sourcepub fn available_challenges(self, input: ChallengeNameType) -> Self
pub fn available_challenges(self, input: ChallengeNameType) -> Self
Appends an item to available_challenges.
To override the contents of this collection use set_available_challenges.
This response parameter lists the available authentication challenges that users can select from in choice-based authentication. For example, they might be able to choose between passkey authentication, a one-time password from an SMS message, and a traditional password.
Sourcepub fn set_available_challenges(
self,
input: Option<Vec<ChallengeNameType>>,
) -> Self
pub fn set_available_challenges( self, input: Option<Vec<ChallengeNameType>>, ) -> Self
This response parameter lists the available authentication challenges that users can select from in choice-based authentication. For example, they might be able to choose between passkey authentication, a one-time password from an SMS message, and a traditional password.
Sourcepub fn get_available_challenges(&self) -> &Option<Vec<ChallengeNameType>>
pub fn get_available_challenges(&self) -> &Option<Vec<ChallengeNameType>>
This response parameter lists the available authentication challenges that users can select from in choice-based authentication. For example, they might be able to choose between passkey authentication, a one-time password from an SMS message, and a traditional password.
Sourcepub fn build(self) -> AdminInitiateAuthOutput
pub fn build(self) -> AdminInitiateAuthOutput
Consumes the builder and constructs a AdminInitiateAuthOutput.
Trait Implementations§
Source§impl Clone for AdminInitiateAuthOutputBuilder
impl Clone for AdminInitiateAuthOutputBuilder
Source§fn clone(&self) -> AdminInitiateAuthOutputBuilder
fn clone(&self) -> AdminInitiateAuthOutputBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Default for AdminInitiateAuthOutputBuilder
impl Default for AdminInitiateAuthOutputBuilder
Source§fn default() -> AdminInitiateAuthOutputBuilder
fn default() -> AdminInitiateAuthOutputBuilder
Source§impl PartialEq for AdminInitiateAuthOutputBuilder
impl PartialEq for AdminInitiateAuthOutputBuilder
Source§fn eq(&self, other: &AdminInitiateAuthOutputBuilder) -> bool
fn eq(&self, other: &AdminInitiateAuthOutputBuilder) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for AdminInitiateAuthOutputBuilder
Auto Trait Implementations§
impl Freeze for AdminInitiateAuthOutputBuilder
impl RefUnwindSafe for AdminInitiateAuthOutputBuilder
impl Send for AdminInitiateAuthOutputBuilder
impl Sync for AdminInitiateAuthOutputBuilder
impl Unpin for AdminInitiateAuthOutputBuilder
impl UnwindSafe for AdminInitiateAuthOutputBuilder
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);