#[non_exhaustive]pub struct UpdateCanaryInput {Show 16 fields
pub name: Option<String>,
pub code: Option<CanaryCodeInput>,
pub execution_role_arn: Option<String>,
pub runtime_version: Option<String>,
pub schedule: Option<CanaryScheduleInput>,
pub run_config: Option<CanaryRunConfigInput>,
pub success_retention_period_in_days: Option<i32>,
pub failure_retention_period_in_days: Option<i32>,
pub vpc_config: Option<VpcConfigInput>,
pub visual_reference: Option<VisualReferenceInput>,
pub artifact_s3_location: Option<String>,
pub artifact_config: Option<ArtifactConfigInput>,
pub provisioned_resource_cleanup: Option<ProvisionedResourceCleanupSetting>,
pub dry_run_id: Option<String>,
pub visual_references: Option<Vec<VisualReferenceInput>>,
pub browser_configs: Option<Vec<BrowserConfig>>,
}
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.name: Option<String>
The name of the canary that you want to update. To find the names of your canaries, use DescribeCanaries.
You cannot change the name of a canary that has already been created.
code: Option<CanaryCodeInput>
A structure that includes the entry point from which the canary should start running your script. If the script is stored in an Amazon S3 bucket, the bucket name, key, and version are also included.
execution_role_arn: Option<String>
The ARN of the IAM role to be used to run the canary. This role must already exist, and must include lambda.amazonaws.com
as a principal in the trust policy. The role must also have the following permissions:
-
s3:PutObject
-
s3:GetBucketLocation
-
s3:ListAllMyBuckets
-
cloudwatch:PutMetricData
-
logs:CreateLogGroup
-
logs:CreateLogStream
-
logs:CreateLogStream
runtime_version: Option<String>
Specifies the runtime version to use for the canary. For a list of valid runtime versions and for more information about runtime versions, see Canary Runtime Versions.
schedule: Option<CanaryScheduleInput>
A structure that contains information about how often the canary is to run, and when these runs are to stop.
run_config: Option<CanaryRunConfigInput>
A structure that contains the timeout value that is used for each individual run of the canary.
Environment variable keys and values are encrypted at rest using Amazon Web Services owned KMS keys. However, the environment variables are not encrypted on the client side. Do not store sensitive information in them.
success_retention_period_in_days: Option<i32>
The number of days to retain data about successful runs of this canary.
This setting affects the range of information returned by GetCanaryRuns, as well as the range of information displayed in the Synthetics console.
failure_retention_period_in_days: Option<i32>
The number of days to retain data about failed runs of this canary.
This setting affects the range of information returned by GetCanaryRuns, as well as the range of information displayed in the Synthetics console.
vpc_config: Option<VpcConfigInput>
If this canary is to test an endpoint in a VPC, this structure contains information about the subnet and security groups of the VPC endpoint. For more information, see Running a Canary in a VPC.
visual_reference: Option<VisualReferenceInput>
Defines the screenshots to use as the baseline for comparisons during visual monitoring comparisons during future runs of this canary. If you omit this parameter, no changes are made to any baseline screenshots that the canary might be using already.
Visual monitoring is supported only on canaries running the syn-puppeteer-node-3.2 runtime or later. For more information, see Visual monitoring and Visual monitoring blueprint
artifact_s3_location: Option<String>
The location in Amazon S3 where Synthetics stores artifacts from the test runs of this canary. Artifacts include the log file, screenshots, and HAR files. The name of the Amazon S3 bucket can't include a period (.).
artifact_config: Option<ArtifactConfigInput>
A structure that contains the configuration for canary artifacts, including the encryption-at-rest settings for artifacts that the canary uploads to Amazon S3.
provisioned_resource_cleanup: Option<ProvisionedResourceCleanupSetting>
Specifies whether to also delete the Lambda functions and layers used by this canary when the canary is deleted.
If the value of this parameter is OFF
, then the value of the DeleteLambda
parameter of the DeleteCanary operation determines whether the Lambda functions and layers will be deleted.
dry_run_id: Option<String>
Update the existing canary using the updated configurations from the DryRun associated with the DryRunId.
When you use the dryRunId
field when updating a canary, the only other field you can provide is the Schedule
. Adding any other field will thrown an exception.
visual_references: Option<Vec<VisualReferenceInput>>
A list of visual reference configurations for the canary, one for each browser type that the canary is configured to run on. Visual references are used for visual monitoring comparisons.
syn-nodejs-puppeteer-11.0
and above, and syn-nodejs-playwright-3.0
and above, only supports visualReferences
. visualReference
field is not supported.
Versions older than syn-nodejs-puppeteer-11.0
supports both visualReference
and visualReferences
for backward compatibility. It is recommended to use visualReferences
for consistency and future compatibility.
For multibrowser visual monitoring, you can update the baseline for all configured browsers in a single update call by specifying a list of VisualReference objects, one per browser. Each VisualReference object maps to a specific browser configuration, allowing you to manage visual baselines for multiple browsers simultaneously.
For single configuration canaries using Chrome browser (default browser), use visualReferences for syn-nodejs-puppeteer-11.0
and above, and syn-nodejs-playwright-3.0
and above canaries. The browserType in the visualReference object is not mandatory.
browser_configs: Option<Vec<BrowserConfig>>
A structure that specifies the browser type to use for a canary run. CloudWatch Synthetics supports running canaries on both CHROME
and FIREFOX
browsers.
If not specified, browserConfigs
defaults to Chrome.
Implementations§
Source§impl UpdateCanaryInput
impl UpdateCanaryInput
Sourcepub fn name(&self) -> Option<&str>
pub fn name(&self) -> Option<&str>
The name of the canary that you want to update. To find the names of your canaries, use DescribeCanaries.
You cannot change the name of a canary that has already been created.
Sourcepub fn code(&self) -> Option<&CanaryCodeInput>
pub fn code(&self) -> Option<&CanaryCodeInput>
A structure that includes the entry point from which the canary should start running your script. If the script is stored in an Amazon S3 bucket, the bucket name, key, and version are also included.
Sourcepub fn execution_role_arn(&self) -> Option<&str>
pub fn execution_role_arn(&self) -> Option<&str>
The ARN of the IAM role to be used to run the canary. This role must already exist, and must include lambda.amazonaws.com
as a principal in the trust policy. The role must also have the following permissions:
-
s3:PutObject
-
s3:GetBucketLocation
-
s3:ListAllMyBuckets
-
cloudwatch:PutMetricData
-
logs:CreateLogGroup
-
logs:CreateLogStream
-
logs:CreateLogStream
Sourcepub fn runtime_version(&self) -> Option<&str>
pub fn runtime_version(&self) -> Option<&str>
Specifies the runtime version to use for the canary. For a list of valid runtime versions and for more information about runtime versions, see Canary Runtime Versions.
Sourcepub fn schedule(&self) -> Option<&CanaryScheduleInput>
pub fn schedule(&self) -> Option<&CanaryScheduleInput>
A structure that contains information about how often the canary is to run, and when these runs are to stop.
Sourcepub fn run_config(&self) -> Option<&CanaryRunConfigInput>
pub fn run_config(&self) -> Option<&CanaryRunConfigInput>
A structure that contains the timeout value that is used for each individual run of the canary.
Environment variable keys and values are encrypted at rest using Amazon Web Services owned KMS keys. However, the environment variables are not encrypted on the client side. Do not store sensitive information in them.
Sourcepub fn success_retention_period_in_days(&self) -> Option<i32>
pub fn success_retention_period_in_days(&self) -> Option<i32>
The number of days to retain data about successful runs of this canary.
This setting affects the range of information returned by GetCanaryRuns, as well as the range of information displayed in the Synthetics console.
Sourcepub fn failure_retention_period_in_days(&self) -> Option<i32>
pub fn failure_retention_period_in_days(&self) -> Option<i32>
The number of days to retain data about failed runs of this canary.
This setting affects the range of information returned by GetCanaryRuns, as well as the range of information displayed in the Synthetics console.
Sourcepub fn vpc_config(&self) -> Option<&VpcConfigInput>
pub fn vpc_config(&self) -> Option<&VpcConfigInput>
If this canary is to test an endpoint in a VPC, this structure contains information about the subnet and security groups of the VPC endpoint. For more information, see Running a Canary in a VPC.
Sourcepub fn visual_reference(&self) -> Option<&VisualReferenceInput>
pub fn visual_reference(&self) -> Option<&VisualReferenceInput>
Defines the screenshots to use as the baseline for comparisons during visual monitoring comparisons during future runs of this canary. If you omit this parameter, no changes are made to any baseline screenshots that the canary might be using already.
Visual monitoring is supported only on canaries running the syn-puppeteer-node-3.2 runtime or later. For more information, see Visual monitoring and Visual monitoring blueprint
Sourcepub fn artifact_s3_location(&self) -> Option<&str>
pub fn artifact_s3_location(&self) -> Option<&str>
The location in Amazon S3 where Synthetics stores artifacts from the test runs of this canary. Artifacts include the log file, screenshots, and HAR files. The name of the Amazon S3 bucket can't include a period (.).
Sourcepub fn artifact_config(&self) -> Option<&ArtifactConfigInput>
pub fn artifact_config(&self) -> Option<&ArtifactConfigInput>
A structure that contains the configuration for canary artifacts, including the encryption-at-rest settings for artifacts that the canary uploads to Amazon S3.
Sourcepub fn provisioned_resource_cleanup(
&self,
) -> Option<&ProvisionedResourceCleanupSetting>
pub fn provisioned_resource_cleanup( &self, ) -> Option<&ProvisionedResourceCleanupSetting>
Specifies whether to also delete the Lambda functions and layers used by this canary when the canary is deleted.
If the value of this parameter is OFF
, then the value of the DeleteLambda
parameter of the DeleteCanary operation determines whether the Lambda functions and layers will be deleted.
Sourcepub fn dry_run_id(&self) -> Option<&str>
pub fn dry_run_id(&self) -> Option<&str>
Update the existing canary using the updated configurations from the DryRun associated with the DryRunId.
When you use the dryRunId
field when updating a canary, the only other field you can provide is the Schedule
. Adding any other field will thrown an exception.
Sourcepub fn visual_references(&self) -> &[VisualReferenceInput]
pub fn visual_references(&self) -> &[VisualReferenceInput]
A list of visual reference configurations for the canary, one for each browser type that the canary is configured to run on. Visual references are used for visual monitoring comparisons.
syn-nodejs-puppeteer-11.0
and above, and syn-nodejs-playwright-3.0
and above, only supports visualReferences
. visualReference
field is not supported.
Versions older than syn-nodejs-puppeteer-11.0
supports both visualReference
and visualReferences
for backward compatibility. It is recommended to use visualReferences
for consistency and future compatibility.
For multibrowser visual monitoring, you can update the baseline for all configured browsers in a single update call by specifying a list of VisualReference objects, one per browser. Each VisualReference object maps to a specific browser configuration, allowing you to manage visual baselines for multiple browsers simultaneously.
For single configuration canaries using Chrome browser (default browser), use visualReferences for syn-nodejs-puppeteer-11.0
and above, and syn-nodejs-playwright-3.0
and above canaries. The browserType in the visualReference object is not mandatory.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .visual_references.is_none()
.
Sourcepub fn browser_configs(&self) -> &[BrowserConfig]
pub fn browser_configs(&self) -> &[BrowserConfig]
A structure that specifies the browser type to use for a canary run. CloudWatch Synthetics supports running canaries on both CHROME
and FIREFOX
browsers.
If not specified, browserConfigs
defaults to Chrome.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .browser_configs.is_none()
.
Source§impl UpdateCanaryInput
impl UpdateCanaryInput
Sourcepub fn builder() -> UpdateCanaryInputBuilder
pub fn builder() -> UpdateCanaryInputBuilder
Creates a new builder-style object to manufacture UpdateCanaryInput
.
Trait Implementations§
Source§impl Clone for UpdateCanaryInput
impl Clone for UpdateCanaryInput
Source§fn clone(&self) -> UpdateCanaryInput
fn clone(&self) -> UpdateCanaryInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for UpdateCanaryInput
impl Debug for UpdateCanaryInput
Source§impl PartialEq for UpdateCanaryInput
impl PartialEq for UpdateCanaryInput
impl StructuralPartialEq for UpdateCanaryInput
Auto Trait Implementations§
impl Freeze for UpdateCanaryInput
impl RefUnwindSafe for UpdateCanaryInput
impl Send for UpdateCanaryInput
impl Sync for UpdateCanaryInput
impl Unpin for UpdateCanaryInput
impl UnwindSafe for UpdateCanaryInput
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);