pub struct CreateAutoScalingConfigurationFluentBuilder { /* private fields */ }Expand description
Fluent builder constructing a request to CreateAutoScalingConfiguration.
Create an App Runner automatic scaling configuration resource. App Runner requires this resource when you create or update App Runner services and you require non-default auto scaling settings. You can share an auto scaling configuration across multiple services.
Create multiple revisions of a configuration by calling this action multiple times using the same AutoScalingConfigurationName. The call returns incremental AutoScalingConfigurationRevision values. When you create a service and configure an auto scaling configuration resource, the service uses the latest active revision of the auto scaling configuration by default. You can optionally configure the service to use a specific revision.
Configure a higher MinSize to increase the spread of your App Runner service over more Availability Zones in the Amazon Web Services Region. The tradeoff is a higher minimal cost.
Configure a lower MaxSize to control your cost. The tradeoff is lower responsiveness during peak demand.
Implementations§
Source§impl CreateAutoScalingConfigurationFluentBuilder
impl CreateAutoScalingConfigurationFluentBuilder
Sourcepub fn as_input(&self) -> &CreateAutoScalingConfigurationInputBuilder
pub fn as_input(&self) -> &CreateAutoScalingConfigurationInputBuilder
Access the CreateAutoScalingConfiguration as a reference.
Sourcepub async fn send(
self,
) -> Result<CreateAutoScalingConfigurationOutput, SdkError<CreateAutoScalingConfigurationError, HttpResponse>>
pub async fn send( self, ) -> Result<CreateAutoScalingConfigurationOutput, SdkError<CreateAutoScalingConfigurationError, HttpResponse>>
Sends the request and returns the response.
If an error occurs, an SdkError will be returned with additional details that
can be matched against.
By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.
Sourcepub fn customize(
self,
) -> CustomizableOperation<CreateAutoScalingConfigurationOutput, CreateAutoScalingConfigurationError, Self>
pub fn customize( self, ) -> CustomizableOperation<CreateAutoScalingConfigurationOutput, CreateAutoScalingConfigurationError, Self>
Consumes this builder, creating a customizable operation that can be modified before being sent.
Sourcepub fn auto_scaling_configuration_name(self, input: impl Into<String>) -> Self
pub fn auto_scaling_configuration_name(self, input: impl Into<String>) -> Self
A name for the auto scaling configuration. When you use it for the first time in an Amazon Web Services Region, App Runner creates revision number 1 of this name. When you use the same name in subsequent calls, App Runner creates incremental revisions of the configuration.
Prior to the release of Auto scale configuration enhancements, the name DefaultConfiguration was reserved.
This restriction is no longer in place. You can now manage DefaultConfiguration the same way you manage your custom auto scaling configurations. This means you can do the following with the DefaultConfiguration that App Runner provides:
-
Create new revisions of the
DefaultConfiguration. -
Delete the revisions of the
DefaultConfiguration. -
Delete the auto scaling configuration for which the App Runner
DefaultConfigurationwas created. -
If you delete the auto scaling configuration you can create another custom auto scaling configuration with the same
DefaultConfigurationname. The originalDefaultConfigurationresource provided by App Runner remains in your account unless you make changes to it.
Sourcepub fn set_auto_scaling_configuration_name(self, input: Option<String>) -> Self
pub fn set_auto_scaling_configuration_name(self, input: Option<String>) -> Self
A name for the auto scaling configuration. When you use it for the first time in an Amazon Web Services Region, App Runner creates revision number 1 of this name. When you use the same name in subsequent calls, App Runner creates incremental revisions of the configuration.
Prior to the release of Auto scale configuration enhancements, the name DefaultConfiguration was reserved.
This restriction is no longer in place. You can now manage DefaultConfiguration the same way you manage your custom auto scaling configurations. This means you can do the following with the DefaultConfiguration that App Runner provides:
-
Create new revisions of the
DefaultConfiguration. -
Delete the revisions of the
DefaultConfiguration. -
Delete the auto scaling configuration for which the App Runner
DefaultConfigurationwas created. -
If you delete the auto scaling configuration you can create another custom auto scaling configuration with the same
DefaultConfigurationname. The originalDefaultConfigurationresource provided by App Runner remains in your account unless you make changes to it.
Sourcepub fn get_auto_scaling_configuration_name(&self) -> &Option<String>
pub fn get_auto_scaling_configuration_name(&self) -> &Option<String>
A name for the auto scaling configuration. When you use it for the first time in an Amazon Web Services Region, App Runner creates revision number 1 of this name. When you use the same name in subsequent calls, App Runner creates incremental revisions of the configuration.
Prior to the release of Auto scale configuration enhancements, the name DefaultConfiguration was reserved.
This restriction is no longer in place. You can now manage DefaultConfiguration the same way you manage your custom auto scaling configurations. This means you can do the following with the DefaultConfiguration that App Runner provides:
-
Create new revisions of the
DefaultConfiguration. -
Delete the revisions of the
DefaultConfiguration. -
Delete the auto scaling configuration for which the App Runner
DefaultConfigurationwas created. -
If you delete the auto scaling configuration you can create another custom auto scaling configuration with the same
DefaultConfigurationname. The originalDefaultConfigurationresource provided by App Runner remains in your account unless you make changes to it.
Sourcepub fn max_concurrency(self, input: i32) -> Self
pub fn max_concurrency(self, input: i32) -> Self
The maximum number of concurrent requests that you want an instance to process. If the number of concurrent requests exceeds this limit, App Runner scales up your service.
Default: 100
Sourcepub fn set_max_concurrency(self, input: Option<i32>) -> Self
pub fn set_max_concurrency(self, input: Option<i32>) -> Self
The maximum number of concurrent requests that you want an instance to process. If the number of concurrent requests exceeds this limit, App Runner scales up your service.
Default: 100
Sourcepub fn get_max_concurrency(&self) -> &Option<i32>
pub fn get_max_concurrency(&self) -> &Option<i32>
The maximum number of concurrent requests that you want an instance to process. If the number of concurrent requests exceeds this limit, App Runner scales up your service.
Default: 100
Sourcepub fn min_size(self, input: i32) -> Self
pub fn min_size(self, input: i32) -> Self
The minimum number of instances that App Runner provisions for your service. The service always has at least MinSize provisioned instances. Some of them actively serve traffic. The rest of them (provisioned and inactive instances) are a cost-effective compute capacity reserve and are ready to be quickly activated. You pay for memory usage of all the provisioned instances. You pay for CPU usage of only the active subset.
App Runner temporarily doubles the number of provisioned instances during deployments, to maintain the same capacity for both old and new code.
Default: 1
Sourcepub fn set_min_size(self, input: Option<i32>) -> Self
pub fn set_min_size(self, input: Option<i32>) -> Self
The minimum number of instances that App Runner provisions for your service. The service always has at least MinSize provisioned instances. Some of them actively serve traffic. The rest of them (provisioned and inactive instances) are a cost-effective compute capacity reserve and are ready to be quickly activated. You pay for memory usage of all the provisioned instances. You pay for CPU usage of only the active subset.
App Runner temporarily doubles the number of provisioned instances during deployments, to maintain the same capacity for both old and new code.
Default: 1
Sourcepub fn get_min_size(&self) -> &Option<i32>
pub fn get_min_size(&self) -> &Option<i32>
The minimum number of instances that App Runner provisions for your service. The service always has at least MinSize provisioned instances. Some of them actively serve traffic. The rest of them (provisioned and inactive instances) are a cost-effective compute capacity reserve and are ready to be quickly activated. You pay for memory usage of all the provisioned instances. You pay for CPU usage of only the active subset.
App Runner temporarily doubles the number of provisioned instances during deployments, to maintain the same capacity for both old and new code.
Default: 1
Sourcepub fn max_size(self, input: i32) -> Self
pub fn max_size(self, input: i32) -> Self
The maximum number of instances that your service scales up to. At most MaxSize instances actively serve traffic for your service.
Default: 25
Sourcepub fn set_max_size(self, input: Option<i32>) -> Self
pub fn set_max_size(self, input: Option<i32>) -> Self
The maximum number of instances that your service scales up to. At most MaxSize instances actively serve traffic for your service.
Default: 25
Sourcepub fn get_max_size(&self) -> &Option<i32>
pub fn get_max_size(&self) -> &Option<i32>
The maximum number of instances that your service scales up to. At most MaxSize instances actively serve traffic for your service.
Default: 25
Appends an item to Tags.
To override the contents of this collection use set_tags.
A list of metadata items that you can associate with your auto scaling configuration resource. A tag is a key-value pair.
A list of metadata items that you can associate with your auto scaling configuration resource. A tag is a key-value pair.
A list of metadata items that you can associate with your auto scaling configuration resource. A tag is a key-value pair.
Trait Implementations§
Source§impl Clone for CreateAutoScalingConfigurationFluentBuilder
impl Clone for CreateAutoScalingConfigurationFluentBuilder
Source§fn clone(&self) -> CreateAutoScalingConfigurationFluentBuilder
fn clone(&self) -> CreateAutoScalingConfigurationFluentBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreAuto Trait Implementations§
impl Freeze for CreateAutoScalingConfigurationFluentBuilder
impl !RefUnwindSafe for CreateAutoScalingConfigurationFluentBuilder
impl Send for CreateAutoScalingConfigurationFluentBuilder
impl Sync for CreateAutoScalingConfigurationFluentBuilder
impl Unpin for CreateAutoScalingConfigurationFluentBuilder
impl !UnwindSafe for CreateAutoScalingConfigurationFluentBuilder
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);