#[non_exhaustive]pub struct TargetGroupAttribute {
pub key: Option<String>,
pub value: Option<String>,
}Expand description
Information about a target group attribute.
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.key: Option<String>The name of the attribute.
The following attributes are supported by all load balancers:
-
deregistration_delay.timeout_seconds- The amount of time, in seconds, for Elastic Load Balancing to wait before changing the state of a deregistering target fromdrainingtounused. The range is 0-3600 seconds. The default value is 300 seconds. If the target is a Lambda function, this attribute is not supported. -
stickiness.enabled- Indicates whether target stickiness is enabled. The value istrueorfalse. The default isfalse. -
stickiness.type- Indicates the type of stickiness. The possible values are:-
lb_cookieandapp_cookiefor Application Load Balancers. -
source_ipfor Network Load Balancers. -
source_ip_dest_ipandsource_ip_dest_ip_protofor Gateway Load Balancers.
-
The following attributes are supported by Application Load Balancers and Network Load Balancers:
-
load_balancing.cross_zone.enabled- Indicates whether cross zone load balancing is enabled. The value istrue,falseoruse_load_balancer_configuration. The default isuse_load_balancer_configuration. -
target_group_health.dns_failover.minimum_healthy_targets.count- The minimum number of targets that must be healthy. If the number of healthy targets is below this value, mark the zone as unhealthy in DNS, so that traffic is routed only to healthy zones. The possible values areoffor an integer from 1 to the maximum number of targets. The default is 1. -
target_group_health.dns_failover.minimum_healthy_targets.percentage- The minimum percentage of targets that must be healthy. If the percentage of healthy targets is below this value, mark the zone as unhealthy in DNS, so that traffic is routed only to healthy zones. The possible values areoffor an integer from 1 to 100. The default isoff. -
target_group_health.unhealthy_state_routing.minimum_healthy_targets.count- The minimum number of targets that must be healthy. If the number of healthy targets is below this value, send traffic to all targets, including unhealthy targets. The possible values are 1 to the maximum number of targets. The default is 1. -
target_group_health.unhealthy_state_routing.minimum_healthy_targets.percentage- The minimum percentage of targets that must be healthy. If the percentage of healthy targets is below this value, send traffic to all targets, including unhealthy targets. The possible values areoffor an integer from 1 to 100. The default isoff.
The following attributes are supported only if the load balancer is an Application Load Balancer and the target is an instance or an IP address:
-
load_balancing.algorithm.type- The load balancing algorithm determines how the load balancer selects targets when routing requests. The value isround_robin,least_outstanding_requests, orweighted_random. The default isround_robin. -
load_balancing.algorithm.anomaly_mitigation- Only available whenload_balancing.algorithm.typeisweighted_random. Indicates whether anomaly mitigation is enabled. The value isonoroff. The default isoff. -
slow_start.duration_seconds- The time period, in seconds, during which a newly registered target receives an increasing share of the traffic to the target group. After this time period ends, the target receives its full share of traffic. The range is 30-900 seconds (15 minutes). The default is 0 seconds (disabled). -
stickiness.app_cookie.cookie_name- Indicates the name of the application-based cookie. Names that start with the following prefixes are not allowed:AWSALB,AWSALBAPP, andAWSALBTG; they're reserved for use by the load balancer. -
stickiness.app_cookie.duration_seconds- The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the application-based cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds). -
stickiness.lb_cookie.duration_seconds- The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the load balancer-generated cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds).
The following attribute is supported only if the load balancer is an Application Load Balancer and the target is a Lambda function:
-
lambda.multi_value_headers.enabled- Indicates whether the request and response headers that are exchanged between the load balancer and the Lambda function include arrays of values or strings. The value istrueorfalse. The default isfalse. If the value isfalseand the request contains a duplicate header field name or query parameter key, the load balancer uses the last value sent by the client.
The following attributes are supported only by Network Load Balancers:
-
deregistration_delay.connection_termination.enabled- Indicates whether the load balancer terminates connections at the end of the deregistration timeout. The value istrueorfalse. For new UDP/TCP_UDP target groups the default istrue. Otherwise, the default isfalse. -
preserve_client_ip.enabled- Indicates whether client IP preservation is enabled. The value istrueorfalse. The default is disabled if the target group type is IP address and the target group protocol is TCP or TLS. Otherwise, the default is enabled. Client IP preservation can't be disabled for UDP and TCP_UDP target groups. -
proxy_protocol_v2.enabled- Indicates whether Proxy Protocol version 2 is enabled. The value istrueorfalse. The default isfalse. -
target_health_state.unhealthy.connection_termination.enabled- Indicates whether the load balancer terminates connections to unhealthy targets. The value istrueorfalse. The default istrue. This attribute can't be enabled for UDP and TCP_UDP target groups. -
target_health_state.unhealthy.draining_interval_seconds- The amount of time for Elastic Load Balancing to wait before changing the state of an unhealthy target fromunhealthy.drainingtounhealthy. The range is 0-360000 seconds. The default value is 0 seconds.Note: This attribute can only be configured when
target_health_state.unhealthy.connection_termination.enabledisfalse.
The following attributes are supported only by Gateway Load Balancers:
-
target_failover.on_deregistration- Indicates how the Gateway Load Balancer handles existing flows when a target is deregistered. The possible values arerebalanceandno_rebalance. The default isno_rebalance. The two attributes (target_failover.on_deregistrationandtarget_failover.on_unhealthy) can't be set independently. The value you set for both attributes must be the same. -
target_failover.on_unhealthy- Indicates how the Gateway Load Balancer handles existing flows when a target is unhealthy. The possible values arerebalanceandno_rebalance. The default isno_rebalance. The two attributes (target_failover.on_deregistrationandtarget_failover.on_unhealthy) can't be set independently. The value you set for both attributes must be the same.
value: Option<String>The value of the attribute.
Implementations§
Source§impl TargetGroupAttribute
impl TargetGroupAttribute
Sourcepub fn key(&self) -> Option<&str>
pub fn key(&self) -> Option<&str>
The name of the attribute.
The following attributes are supported by all load balancers:
-
deregistration_delay.timeout_seconds- The amount of time, in seconds, for Elastic Load Balancing to wait before changing the state of a deregistering target fromdrainingtounused. The range is 0-3600 seconds. The default value is 300 seconds. If the target is a Lambda function, this attribute is not supported. -
stickiness.enabled- Indicates whether target stickiness is enabled. The value istrueorfalse. The default isfalse. -
stickiness.type- Indicates the type of stickiness. The possible values are:-
lb_cookieandapp_cookiefor Application Load Balancers. -
source_ipfor Network Load Balancers. -
source_ip_dest_ipandsource_ip_dest_ip_protofor Gateway Load Balancers.
-
The following attributes are supported by Application Load Balancers and Network Load Balancers:
-
load_balancing.cross_zone.enabled- Indicates whether cross zone load balancing is enabled. The value istrue,falseoruse_load_balancer_configuration. The default isuse_load_balancer_configuration. -
target_group_health.dns_failover.minimum_healthy_targets.count- The minimum number of targets that must be healthy. If the number of healthy targets is below this value, mark the zone as unhealthy in DNS, so that traffic is routed only to healthy zones. The possible values areoffor an integer from 1 to the maximum number of targets. The default is 1. -
target_group_health.dns_failover.minimum_healthy_targets.percentage- The minimum percentage of targets that must be healthy. If the percentage of healthy targets is below this value, mark the zone as unhealthy in DNS, so that traffic is routed only to healthy zones. The possible values areoffor an integer from 1 to 100. The default isoff. -
target_group_health.unhealthy_state_routing.minimum_healthy_targets.count- The minimum number of targets that must be healthy. If the number of healthy targets is below this value, send traffic to all targets, including unhealthy targets. The possible values are 1 to the maximum number of targets. The default is 1. -
target_group_health.unhealthy_state_routing.minimum_healthy_targets.percentage- The minimum percentage of targets that must be healthy. If the percentage of healthy targets is below this value, send traffic to all targets, including unhealthy targets. The possible values areoffor an integer from 1 to 100. The default isoff.
The following attributes are supported only if the load balancer is an Application Load Balancer and the target is an instance or an IP address:
-
load_balancing.algorithm.type- The load balancing algorithm determines how the load balancer selects targets when routing requests. The value isround_robin,least_outstanding_requests, orweighted_random. The default isround_robin. -
load_balancing.algorithm.anomaly_mitigation- Only available whenload_balancing.algorithm.typeisweighted_random. Indicates whether anomaly mitigation is enabled. The value isonoroff. The default isoff. -
slow_start.duration_seconds- The time period, in seconds, during which a newly registered target receives an increasing share of the traffic to the target group. After this time period ends, the target receives its full share of traffic. The range is 30-900 seconds (15 minutes). The default is 0 seconds (disabled). -
stickiness.app_cookie.cookie_name- Indicates the name of the application-based cookie. Names that start with the following prefixes are not allowed:AWSALB,AWSALBAPP, andAWSALBTG; they're reserved for use by the load balancer. -
stickiness.app_cookie.duration_seconds- The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the application-based cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds). -
stickiness.lb_cookie.duration_seconds- The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the load balancer-generated cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds).
The following attribute is supported only if the load balancer is an Application Load Balancer and the target is a Lambda function:
-
lambda.multi_value_headers.enabled- Indicates whether the request and response headers that are exchanged between the load balancer and the Lambda function include arrays of values or strings. The value istrueorfalse. The default isfalse. If the value isfalseand the request contains a duplicate header field name or query parameter key, the load balancer uses the last value sent by the client.
The following attributes are supported only by Network Load Balancers:
-
deregistration_delay.connection_termination.enabled- Indicates whether the load balancer terminates connections at the end of the deregistration timeout. The value istrueorfalse. For new UDP/TCP_UDP target groups the default istrue. Otherwise, the default isfalse. -
preserve_client_ip.enabled- Indicates whether client IP preservation is enabled. The value istrueorfalse. The default is disabled if the target group type is IP address and the target group protocol is TCP or TLS. Otherwise, the default is enabled. Client IP preservation can't be disabled for UDP and TCP_UDP target groups. -
proxy_protocol_v2.enabled- Indicates whether Proxy Protocol version 2 is enabled. The value istrueorfalse. The default isfalse. -
target_health_state.unhealthy.connection_termination.enabled- Indicates whether the load balancer terminates connections to unhealthy targets. The value istrueorfalse. The default istrue. This attribute can't be enabled for UDP and TCP_UDP target groups. -
target_health_state.unhealthy.draining_interval_seconds- The amount of time for Elastic Load Balancing to wait before changing the state of an unhealthy target fromunhealthy.drainingtounhealthy. The range is 0-360000 seconds. The default value is 0 seconds.Note: This attribute can only be configured when
target_health_state.unhealthy.connection_termination.enabledisfalse.
The following attributes are supported only by Gateway Load Balancers:
-
target_failover.on_deregistration- Indicates how the Gateway Load Balancer handles existing flows when a target is deregistered. The possible values arerebalanceandno_rebalance. The default isno_rebalance. The two attributes (target_failover.on_deregistrationandtarget_failover.on_unhealthy) can't be set independently. The value you set for both attributes must be the same. -
target_failover.on_unhealthy- Indicates how the Gateway Load Balancer handles existing flows when a target is unhealthy. The possible values arerebalanceandno_rebalance. The default isno_rebalance. The two attributes (target_failover.on_deregistrationandtarget_failover.on_unhealthy) can't be set independently. The value you set for both attributes must be the same.
Source§impl TargetGroupAttribute
impl TargetGroupAttribute
Sourcepub fn builder() -> TargetGroupAttributeBuilder
pub fn builder() -> TargetGroupAttributeBuilder
Creates a new builder-style object to manufacture TargetGroupAttribute.
Trait Implementations§
Source§impl Clone for TargetGroupAttribute
impl Clone for TargetGroupAttribute
Source§fn clone(&self) -> TargetGroupAttribute
fn clone(&self) -> TargetGroupAttribute
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for TargetGroupAttribute
impl Debug for TargetGroupAttribute
Source§impl PartialEq for TargetGroupAttribute
impl PartialEq for TargetGroupAttribute
impl StructuralPartialEq for TargetGroupAttribute
Auto Trait Implementations§
impl Freeze for TargetGroupAttribute
impl RefUnwindSafe for TargetGroupAttribute
impl Send for TargetGroupAttribute
impl Sync for TargetGroupAttribute
impl Unpin for TargetGroupAttribute
impl UnwindSafe for TargetGroupAttribute
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);