#[non_exhaustive]pub struct CreateResolverRuleInput {
pub creator_request_id: Option<String>,
pub name: Option<String>,
pub rule_type: Option<RuleTypeOption>,
pub domain_name: Option<String>,
pub target_ips: Option<Vec<TargetAddress>>,
pub resolver_endpoint_id: Option<String>,
pub tags: Option<Vec<Tag>>,
pub delegation_record: 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.creator_request_id: Option<String>
A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation twice. CreatorRequestId
can be any unique string, for example, a date/time stamp.
name: Option<String>
A friendly name that lets you easily find a rule in the Resolver dashboard in the Route 53 console.
rule_type: Option<RuleTypeOption>
When you want to forward DNS queries for specified domain name to resolvers on your network, specify FORWARD
or DELEGATE
.
When you have a forwarding rule to forward DNS queries for a domain to your network and you want Resolver to process queries for a subdomain of that domain, specify SYSTEM
.
For example, to forward DNS queries for example.com to resolvers on your network, you create a rule and specify FORWARD
for RuleType
. To then have Resolver process queries for apex.example.com, you create a rule and specify SYSTEM
for RuleType
.
Currently, only Resolver can create rules that have a value of RECURSIVE
for RuleType
.
domain_name: Option<String>
DNS queries for this domain name are forwarded to the IP addresses that you specify in TargetIps
. If a query matches multiple Resolver rules (example.com and www.example.com), outbound DNS queries are routed using the Resolver rule that contains the most specific domain name (www.example.com).
target_ips: Option<Vec<TargetAddress>>
The IPs that you want Resolver to forward DNS queries to. You can specify either Ipv4 or Ipv6 addresses but not both in the same rule. Separate IP addresses with a space.
TargetIps
is available only when the value of Rule type
is FORWARD
.
resolver_endpoint_id: Option<String>
The ID of the outbound Resolver endpoint that you want to use to route DNS queries to the IP addresses that you specify in TargetIps
.
A list of the tag keys and values that you want to associate with the endpoint.
delegation_record: Option<String>
DNS queries with the delegation records that match this domain name are forwarded to the resolvers on your network.
Implementations§
Source§impl CreateResolverRuleInput
impl CreateResolverRuleInput
Sourcepub fn creator_request_id(&self) -> Option<&str>
pub fn creator_request_id(&self) -> Option<&str>
A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation twice. CreatorRequestId
can be any unique string, for example, a date/time stamp.
Sourcepub fn name(&self) -> Option<&str>
pub fn name(&self) -> Option<&str>
A friendly name that lets you easily find a rule in the Resolver dashboard in the Route 53 console.
Sourcepub fn rule_type(&self) -> Option<&RuleTypeOption>
pub fn rule_type(&self) -> Option<&RuleTypeOption>
When you want to forward DNS queries for specified domain name to resolvers on your network, specify FORWARD
or DELEGATE
.
When you have a forwarding rule to forward DNS queries for a domain to your network and you want Resolver to process queries for a subdomain of that domain, specify SYSTEM
.
For example, to forward DNS queries for example.com to resolvers on your network, you create a rule and specify FORWARD
for RuleType
. To then have Resolver process queries for apex.example.com, you create a rule and specify SYSTEM
for RuleType
.
Currently, only Resolver can create rules that have a value of RECURSIVE
for RuleType
.
Sourcepub fn domain_name(&self) -> Option<&str>
pub fn domain_name(&self) -> Option<&str>
DNS queries for this domain name are forwarded to the IP addresses that you specify in TargetIps
. If a query matches multiple Resolver rules (example.com and www.example.com), outbound DNS queries are routed using the Resolver rule that contains the most specific domain name (www.example.com).
Sourcepub fn target_ips(&self) -> &[TargetAddress]
pub fn target_ips(&self) -> &[TargetAddress]
The IPs that you want Resolver to forward DNS queries to. You can specify either Ipv4 or Ipv6 addresses but not both in the same rule. Separate IP addresses with a space.
TargetIps
is available only when the value of Rule type
is FORWARD
.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .target_ips.is_none()
.
Sourcepub fn resolver_endpoint_id(&self) -> Option<&str>
pub fn resolver_endpoint_id(&self) -> Option<&str>
The ID of the outbound Resolver endpoint that you want to use to route DNS queries to the IP addresses that you specify in TargetIps
.
A list of the tag keys and values that you want to associate with the endpoint.
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 delegation_record(&self) -> Option<&str>
pub fn delegation_record(&self) -> Option<&str>
DNS queries with the delegation records that match this domain name are forwarded to the resolvers on your network.
Source§impl CreateResolverRuleInput
impl CreateResolverRuleInput
Sourcepub fn builder() -> CreateResolverRuleInputBuilder
pub fn builder() -> CreateResolverRuleInputBuilder
Creates a new builder-style object to manufacture CreateResolverRuleInput
.
Trait Implementations§
Source§impl Clone for CreateResolverRuleInput
impl Clone for CreateResolverRuleInput
Source§fn clone(&self) -> CreateResolverRuleInput
fn clone(&self) -> CreateResolverRuleInput
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for CreateResolverRuleInput
impl Debug for CreateResolverRuleInput
Source§impl PartialEq for CreateResolverRuleInput
impl PartialEq for CreateResolverRuleInput
Source§fn eq(&self, other: &CreateResolverRuleInput) -> bool
fn eq(&self, other: &CreateResolverRuleInput) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for CreateResolverRuleInput
Auto Trait Implementations§
impl Freeze for CreateResolverRuleInput
impl RefUnwindSafe for CreateResolverRuleInput
impl Send for CreateResolverRuleInput
impl Sync for CreateResolverRuleInput
impl Unpin for CreateResolverRuleInput
impl UnwindSafe for CreateResolverRuleInput
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);