#[non_exhaustive]pub struct StartChangeRequestExecutionInput {
pub scheduled_time: Option<DateTime>,
pub document_name: Option<String>,
pub document_version: Option<String>,
pub parameters: Option<HashMap<String, Vec<String>>>,
pub change_request_name: Option<String>,
pub client_token: Option<String>,
pub auto_approve: Option<bool>,
pub runbooks: Option<Vec<Runbook>>,
pub tags: Option<Vec<Tag>>,
pub scheduled_end_time: Option<DateTime>,
pub change_details: Option<String>,
}
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.scheduled_time: Option<DateTime>
The date and time specified in the change request to run the Automation runbooks.
The Automation runbooks specified for the runbook workflow can't run until all required approvals for the change request have been received.
document_name: Option<String>
The name of the change template document to run during the runbook workflow.
document_version: Option<String>
The version of the change template document to run during the runbook workflow.
parameters: Option<HashMap<String, Vec<String>>>
A key-value map of parameters that match the declared parameters in the change template document.
change_request_name: Option<String>
The name of the change request associated with the runbook workflow to be run.
client_token: Option<String>
The user-provided idempotency token. The token must be unique, is case insensitive, enforces the UUID format, and can't be reused.
auto_approve: Option<bool>
Indicates whether the change request can be approved automatically without the need for manual approvals.
If AutoApprovable
is enabled in a change template, then setting AutoApprove
to true
in StartChangeRequestExecution
creates a change request that bypasses approver review.
Change Calendar restrictions are not bypassed in this scenario. If the state of an associated calendar is CLOSED
, change freeze approvers must still grant permission for this change request to run. If they don't, the change won't be processed until the calendar state is again OPEN
.
runbooks: Option<Vec<Runbook>>
Information about the Automation runbooks that are run during the runbook workflow.
The Automation runbooks specified for the runbook workflow can't run until all required approvals for the change request have been received.
Optional metadata that you assign to a resource. You can specify a maximum of five tags for a change request. 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 change request to identify an environment or target Amazon Web Services Region. In this case, you could specify the following key-value pairs:
-
Key=Environment,Value=Production
-
Key=Region,Value=us-east-2
The Array Members
maximum value is reported as 1000. This number includes capacity reserved for internal operations. When calling the StartChangeRequestExecution
action, you can specify a maximum of 5 tags. You can, however, use the AddTagsToResource
action to add up to a total of 50 tags to an existing change request configuration.
scheduled_end_time: Option<DateTime>
The time that the requester expects the runbook workflow related to the change request to complete. The time is an estimate only that the requester provides for reviewers.
change_details: Option<String>
User-provided details about the change. If no details are provided, content specified in the Template information section of the associated change template is added.
Implementations§
Source§impl StartChangeRequestExecutionInput
impl StartChangeRequestExecutionInput
Sourcepub fn scheduled_time(&self) -> Option<&DateTime>
pub fn scheduled_time(&self) -> Option<&DateTime>
The date and time specified in the change request to run the Automation runbooks.
The Automation runbooks specified for the runbook workflow can't run until all required approvals for the change request have been received.
Sourcepub fn document_name(&self) -> Option<&str>
pub fn document_name(&self) -> Option<&str>
The name of the change template document to run during the runbook workflow.
Sourcepub fn document_version(&self) -> Option<&str>
pub fn document_version(&self) -> Option<&str>
The version of the change template document to run during the runbook workflow.
Sourcepub fn parameters(&self) -> Option<&HashMap<String, Vec<String>>>
pub fn parameters(&self) -> Option<&HashMap<String, Vec<String>>>
A key-value map of parameters that match the declared parameters in the change template document.
Sourcepub fn change_request_name(&self) -> Option<&str>
pub fn change_request_name(&self) -> Option<&str>
The name of the change request associated with the runbook workflow to be run.
Sourcepub fn client_token(&self) -> Option<&str>
pub fn client_token(&self) -> Option<&str>
The user-provided idempotency token. The token must be unique, is case insensitive, enforces the UUID format, and can't be reused.
Sourcepub fn auto_approve(&self) -> Option<bool>
pub fn auto_approve(&self) -> Option<bool>
Indicates whether the change request can be approved automatically without the need for manual approvals.
If AutoApprovable
is enabled in a change template, then setting AutoApprove
to true
in StartChangeRequestExecution
creates a change request that bypasses approver review.
Change Calendar restrictions are not bypassed in this scenario. If the state of an associated calendar is CLOSED
, change freeze approvers must still grant permission for this change request to run. If they don't, the change won't be processed until the calendar state is again OPEN
.
Sourcepub fn runbooks(&self) -> &[Runbook]
pub fn runbooks(&self) -> &[Runbook]
Information about the Automation runbooks that are run during the runbook workflow.
The Automation runbooks specified for the runbook workflow can't run until all required approvals for the change request have been received.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .runbooks.is_none()
.
Optional metadata that you assign to a resource. You can specify a maximum of five tags for a change request. 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 change request to identify an environment or target Amazon Web Services Region. In this case, you could specify the following key-value pairs:
-
Key=Environment,Value=Production
-
Key=Region,Value=us-east-2
The Array Members
maximum value is reported as 1000. This number includes capacity reserved for internal operations. When calling the StartChangeRequestExecution
action, you can specify a maximum of 5 tags. You can, however, use the AddTagsToResource
action to add up to a total of 50 tags to an existing change request configuration.
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()
.
Sourcepub fn scheduled_end_time(&self) -> Option<&DateTime>
pub fn scheduled_end_time(&self) -> Option<&DateTime>
The time that the requester expects the runbook workflow related to the change request to complete. The time is an estimate only that the requester provides for reviewers.
Sourcepub fn change_details(&self) -> Option<&str>
pub fn change_details(&self) -> Option<&str>
User-provided details about the change. If no details are provided, content specified in the Template information section of the associated change template is added.
Source§impl StartChangeRequestExecutionInput
impl StartChangeRequestExecutionInput
Sourcepub fn builder() -> StartChangeRequestExecutionInputBuilder
pub fn builder() -> StartChangeRequestExecutionInputBuilder
Creates a new builder-style object to manufacture StartChangeRequestExecutionInput
.
Trait Implementations§
Source§impl Clone for StartChangeRequestExecutionInput
impl Clone for StartChangeRequestExecutionInput
Source§fn clone(&self) -> StartChangeRequestExecutionInput
fn clone(&self) -> StartChangeRequestExecutionInput
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for StartChangeRequestExecutionInput
impl PartialEq for StartChangeRequestExecutionInput
Source§fn eq(&self, other: &StartChangeRequestExecutionInput) -> bool
fn eq(&self, other: &StartChangeRequestExecutionInput) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for StartChangeRequestExecutionInput
Auto Trait Implementations§
impl Freeze for StartChangeRequestExecutionInput
impl RefUnwindSafe for StartChangeRequestExecutionInput
impl Send for StartChangeRequestExecutionInput
impl Sync for StartChangeRequestExecutionInput
impl Unpin for StartChangeRequestExecutionInput
impl UnwindSafe for StartChangeRequestExecutionInput
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);