#[non_exhaustive]pub struct CreateLoadBalancerInputBuilder { /* private fields */ }
Expand description
A builder for CreateLoadBalancerInput
.
Implementations§
Source§impl CreateLoadBalancerInputBuilder
impl CreateLoadBalancerInputBuilder
Sourcepub fn name(self, input: impl Into<String>) -> Self
pub fn name(self, input: impl Into<String>) -> Self
The name of the load balancer.
This name must be unique per region per account, can have a maximum of 32 characters, must contain only alphanumeric characters or hyphens, must not begin or end with a hyphen, and must not begin with "internal-".
This field is required.Sourcepub fn set_name(self, input: Option<String>) -> Self
pub fn set_name(self, input: Option<String>) -> Self
The name of the load balancer.
This name must be unique per region per account, can have a maximum of 32 characters, must contain only alphanumeric characters or hyphens, must not begin or end with a hyphen, and must not begin with "internal-".
Sourcepub fn get_name(&self) -> &Option<String>
pub fn get_name(&self) -> &Option<String>
The name of the load balancer.
This name must be unique per region per account, can have a maximum of 32 characters, must contain only alphanumeric characters or hyphens, must not begin or end with a hyphen, and must not begin with "internal-".
Sourcepub fn subnets(self, input: impl Into<String>) -> Self
pub fn subnets(self, input: impl Into<String>) -> Self
Appends an item to subnets
.
To override the contents of this collection use set_subnets
.
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both. To specify an Elastic IP address, specify subnet mappings instead of subnets.
\[Application Load Balancers\] You must specify subnets from at least two Availability Zones.
\[Application Load Balancers on Outposts\] You must specify one Outpost subnet.
\[Application Load Balancers on Local Zones\] You can specify subnets from one or more Local Zones.
\[Network Load Balancers and Gateway Load Balancers\] You can specify subnets from one or more Availability Zones.
Sourcepub fn set_subnets(self, input: Option<Vec<String>>) -> Self
pub fn set_subnets(self, input: Option<Vec<String>>) -> Self
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both. To specify an Elastic IP address, specify subnet mappings instead of subnets.
\[Application Load Balancers\] You must specify subnets from at least two Availability Zones.
\[Application Load Balancers on Outposts\] You must specify one Outpost subnet.
\[Application Load Balancers on Local Zones\] You can specify subnets from one or more Local Zones.
\[Network Load Balancers and Gateway Load Balancers\] You can specify subnets from one or more Availability Zones.
Sourcepub fn get_subnets(&self) -> &Option<Vec<String>>
pub fn get_subnets(&self) -> &Option<Vec<String>>
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both. To specify an Elastic IP address, specify subnet mappings instead of subnets.
\[Application Load Balancers\] You must specify subnets from at least two Availability Zones.
\[Application Load Balancers on Outposts\] You must specify one Outpost subnet.
\[Application Load Balancers on Local Zones\] You can specify subnets from one or more Local Zones.
\[Network Load Balancers and Gateway Load Balancers\] You can specify subnets from one or more Availability Zones.
Sourcepub fn subnet_mappings(self, input: SubnetMapping) -> Self
pub fn subnet_mappings(self, input: SubnetMapping) -> Self
Appends an item to subnet_mappings
.
To override the contents of this collection use set_subnet_mappings
.
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both.
\[Application Load Balancers\] You must specify subnets from at least two Availability Zones. You can't specify Elastic IP addresses for your subnets.
\[Application Load Balancers on Outposts\] You must specify one Outpost subnet.
\[Application Load Balancers on Local Zones\] You can specify subnets from one or more Local Zones.
\[Network Load Balancers\] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. For internet-facing load balancer, you can specify one IPv6 address per subnet.
\[Gateway Load Balancers\] You can specify subnets from one or more Availability Zones. You can't specify Elastic IP addresses for your subnets.
Sourcepub fn set_subnet_mappings(self, input: Option<Vec<SubnetMapping>>) -> Self
pub fn set_subnet_mappings(self, input: Option<Vec<SubnetMapping>>) -> Self
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both.
\[Application Load Balancers\] You must specify subnets from at least two Availability Zones. You can't specify Elastic IP addresses for your subnets.
\[Application Load Balancers on Outposts\] You must specify one Outpost subnet.
\[Application Load Balancers on Local Zones\] You can specify subnets from one or more Local Zones.
\[Network Load Balancers\] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. For internet-facing load balancer, you can specify one IPv6 address per subnet.
\[Gateway Load Balancers\] You can specify subnets from one or more Availability Zones. You can't specify Elastic IP addresses for your subnets.
Sourcepub fn get_subnet_mappings(&self) -> &Option<Vec<SubnetMapping>>
pub fn get_subnet_mappings(&self) -> &Option<Vec<SubnetMapping>>
The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both.
\[Application Load Balancers\] You must specify subnets from at least two Availability Zones. You can't specify Elastic IP addresses for your subnets.
\[Application Load Balancers on Outposts\] You must specify one Outpost subnet.
\[Application Load Balancers on Local Zones\] You can specify subnets from one or more Local Zones.
\[Network Load Balancers\] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. For internet-facing load balancer, you can specify one IPv6 address per subnet.
\[Gateway Load Balancers\] You can specify subnets from one or more Availability Zones. You can't specify Elastic IP addresses for your subnets.
Sourcepub fn security_groups(self, input: impl Into<String>) -> Self
pub fn security_groups(self, input: impl Into<String>) -> Self
Appends an item to security_groups
.
To override the contents of this collection use set_security_groups
.
\[Application Load Balancers and Network Load Balancers\] The IDs of the security groups for the load balancer.
Sourcepub fn set_security_groups(self, input: Option<Vec<String>>) -> Self
pub fn set_security_groups(self, input: Option<Vec<String>>) -> Self
\[Application Load Balancers and Network Load Balancers\] The IDs of the security groups for the load balancer.
Sourcepub fn get_security_groups(&self) -> &Option<Vec<String>>
pub fn get_security_groups(&self) -> &Option<Vec<String>>
\[Application Load Balancers and Network Load Balancers\] The IDs of the security groups for the load balancer.
Sourcepub fn scheme(self, input: LoadBalancerSchemeEnum) -> Self
pub fn scheme(self, input: LoadBalancerSchemeEnum) -> Self
The nodes of an Internet-facing load balancer have public IP addresses. The DNS name of an Internet-facing load balancer is publicly resolvable to the public IP addresses of the nodes. Therefore, Internet-facing load balancers can route requests from clients over the internet.
The nodes of an internal load balancer have only private IP addresses. The DNS name of an internal load balancer is publicly resolvable to the private IP addresses of the nodes. Therefore, internal load balancers can route requests only from clients with access to the VPC for the load balancer.
The default is an Internet-facing load balancer.
You can't specify a scheme for a Gateway Load Balancer.
Sourcepub fn set_scheme(self, input: Option<LoadBalancerSchemeEnum>) -> Self
pub fn set_scheme(self, input: Option<LoadBalancerSchemeEnum>) -> Self
The nodes of an Internet-facing load balancer have public IP addresses. The DNS name of an Internet-facing load balancer is publicly resolvable to the public IP addresses of the nodes. Therefore, Internet-facing load balancers can route requests from clients over the internet.
The nodes of an internal load balancer have only private IP addresses. The DNS name of an internal load balancer is publicly resolvable to the private IP addresses of the nodes. Therefore, internal load balancers can route requests only from clients with access to the VPC for the load balancer.
The default is an Internet-facing load balancer.
You can't specify a scheme for a Gateway Load Balancer.
Sourcepub fn get_scheme(&self) -> &Option<LoadBalancerSchemeEnum>
pub fn get_scheme(&self) -> &Option<LoadBalancerSchemeEnum>
The nodes of an Internet-facing load balancer have public IP addresses. The DNS name of an Internet-facing load balancer is publicly resolvable to the public IP addresses of the nodes. Therefore, Internet-facing load balancers can route requests from clients over the internet.
The nodes of an internal load balancer have only private IP addresses. The DNS name of an internal load balancer is publicly resolvable to the private IP addresses of the nodes. Therefore, internal load balancers can route requests only from clients with access to the VPC for the load balancer.
The default is an Internet-facing load balancer.
You can't specify a scheme for a Gateway Load Balancer.
Appends an item to tags
.
To override the contents of this collection use set_tags
.
The tags to assign to the load balancer.
The tags to assign to the load balancer.
The tags to assign to the load balancer.
Sourcepub fn type(self, input: LoadBalancerTypeEnum) -> Self
pub fn type(self, input: LoadBalancerTypeEnum) -> Self
The type of load balancer. The default is application
.
Sourcepub fn set_type(self, input: Option<LoadBalancerTypeEnum>) -> Self
pub fn set_type(self, input: Option<LoadBalancerTypeEnum>) -> Self
The type of load balancer. The default is application
.
Sourcepub fn get_type(&self) -> &Option<LoadBalancerTypeEnum>
pub fn get_type(&self) -> &Option<LoadBalancerTypeEnum>
The type of load balancer. The default is application
.
Sourcepub fn ip_address_type(self, input: IpAddressType) -> Self
pub fn ip_address_type(self, input: IpAddressType) -> Self
The IP address type. Internal load balancers must use ipv4
.
\[Application Load Balancers\] The possible values are ipv4 (IPv4 addresses), dualstack (IPv4 and IPv6 addresses), and dualstack-without-public-ipv4 (public IPv6 addresses and private IPv4 and IPv6 addresses).
\[Network Load Balancers and Gateway Load Balancers\] The possible values are ipv4 (IPv4 addresses) and dualstack (IPv4 and IPv6 addresses).
Sourcepub fn set_ip_address_type(self, input: Option<IpAddressType>) -> Self
pub fn set_ip_address_type(self, input: Option<IpAddressType>) -> Self
The IP address type. Internal load balancers must use ipv4
.
\[Application Load Balancers\] The possible values are ipv4 (IPv4 addresses), dualstack (IPv4 and IPv6 addresses), and dualstack-without-public-ipv4 (public IPv6 addresses and private IPv4 and IPv6 addresses).
\[Network Load Balancers and Gateway Load Balancers\] The possible values are ipv4 (IPv4 addresses) and dualstack (IPv4 and IPv6 addresses).
Sourcepub fn get_ip_address_type(&self) -> &Option<IpAddressType>
pub fn get_ip_address_type(&self) -> &Option<IpAddressType>
The IP address type. Internal load balancers must use ipv4
.
\[Application Load Balancers\] The possible values are ipv4 (IPv4 addresses), dualstack (IPv4 and IPv6 addresses), and dualstack-without-public-ipv4 (public IPv6 addresses and private IPv4 and IPv6 addresses).
\[Network Load Balancers and Gateway Load Balancers\] The possible values are ipv4 (IPv4 addresses) and dualstack (IPv4 and IPv6 addresses).
Sourcepub fn customer_owned_ipv4_pool(self, input: impl Into<String>) -> Self
pub fn customer_owned_ipv4_pool(self, input: impl Into<String>) -> Self
\[Application Load Balancers on Outposts\] The ID of the customer-owned address pool (CoIP pool).
Sourcepub fn set_customer_owned_ipv4_pool(self, input: Option<String>) -> Self
pub fn set_customer_owned_ipv4_pool(self, input: Option<String>) -> Self
\[Application Load Balancers on Outposts\] The ID of the customer-owned address pool (CoIP pool).
Sourcepub fn get_customer_owned_ipv4_pool(&self) -> &Option<String>
pub fn get_customer_owned_ipv4_pool(&self) -> &Option<String>
\[Application Load Balancers on Outposts\] The ID of the customer-owned address pool (CoIP pool).
Sourcepub fn enable_prefix_for_ipv6_source_nat(
self,
input: EnablePrefixForIpv6SourceNatEnum,
) -> Self
pub fn enable_prefix_for_ipv6_source_nat( self, input: EnablePrefixForIpv6SourceNatEnum, ) -> Self
\[Network Load Balancers with UDP listeners\] Indicates whether to use an IPv6 prefix from each subnet for source NAT. The IP address type must be dualstack. The default value is off.
Sourcepub fn set_enable_prefix_for_ipv6_source_nat(
self,
input: Option<EnablePrefixForIpv6SourceNatEnum>,
) -> Self
pub fn set_enable_prefix_for_ipv6_source_nat( self, input: Option<EnablePrefixForIpv6SourceNatEnum>, ) -> Self
\[Network Load Balancers with UDP listeners\] Indicates whether to use an IPv6 prefix from each subnet for source NAT. The IP address type must be dualstack. The default value is off.
Sourcepub fn get_enable_prefix_for_ipv6_source_nat(
&self,
) -> &Option<EnablePrefixForIpv6SourceNatEnum>
pub fn get_enable_prefix_for_ipv6_source_nat( &self, ) -> &Option<EnablePrefixForIpv6SourceNatEnum>
\[Network Load Balancers with UDP listeners\] Indicates whether to use an IPv6 prefix from each subnet for source NAT. The IP address type must be dualstack. The default value is off.
Sourcepub fn build(self) -> Result<CreateLoadBalancerInput, BuildError>
pub fn build(self) -> Result<CreateLoadBalancerInput, BuildError>
Consumes the builder and constructs a CreateLoadBalancerInput
.
Source§impl CreateLoadBalancerInputBuilder
impl CreateLoadBalancerInputBuilder
Sourcepub async fn send_with(
self,
client: &Client,
) -> Result<CreateLoadBalancerOutput, SdkError<CreateLoadBalancerError, HttpResponse>>
pub async fn send_with( self, client: &Client, ) -> Result<CreateLoadBalancerOutput, SdkError<CreateLoadBalancerError, HttpResponse>>
Sends a request with this input using the given client.
Trait Implementations§
Source§impl Clone for CreateLoadBalancerInputBuilder
impl Clone for CreateLoadBalancerInputBuilder
Source§fn clone(&self) -> CreateLoadBalancerInputBuilder
fn clone(&self) -> CreateLoadBalancerInputBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Default for CreateLoadBalancerInputBuilder
impl Default for CreateLoadBalancerInputBuilder
Source§fn default() -> CreateLoadBalancerInputBuilder
fn default() -> CreateLoadBalancerInputBuilder
Source§impl PartialEq for CreateLoadBalancerInputBuilder
impl PartialEq for CreateLoadBalancerInputBuilder
Source§fn eq(&self, other: &CreateLoadBalancerInputBuilder) -> bool
fn eq(&self, other: &CreateLoadBalancerInputBuilder) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for CreateLoadBalancerInputBuilder
Auto Trait Implementations§
impl Freeze for CreateLoadBalancerInputBuilder
impl RefUnwindSafe for CreateLoadBalancerInputBuilder
impl Send for CreateLoadBalancerInputBuilder
impl Sync for CreateLoadBalancerInputBuilder
impl Unpin for CreateLoadBalancerInputBuilder
impl UnwindSafe for CreateLoadBalancerInputBuilder
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>
Returns self
with the
fg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.bright_black());
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>
Returns self
with the
fg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.bright_green());
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.bright_yellow());
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>
Returns self
with the
fg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.bright_magenta());
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>
Returns self
with the
fg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.bright_white());
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>
Returns self
with the
bg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.on_bright_black());
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>
Returns self
with the
bg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.on_bright_green());
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.on_bright_yellow());
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlue
.
§Example
println!("{}", value.on_bright_blue());
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.on_bright_magenta());
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightCyan
.
§Example
println!("{}", value.on_bright_cyan());
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.on_bright_white());
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 underline(&self) -> Painted<&T>
fn underline(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::Underline
.
§Example
println!("{}", value.underline());
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::RapidBlink
.
§Example
println!("{}", value.rapid_blink());
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);