#[non_exhaustive]pub struct ListResolverQueryLogConfigsInput {
pub max_results: Option<i32>,
pub next_token: Option<String>,
pub filters: Option<Vec<Filter>>,
pub sort_by: Option<String>,
pub sort_order: Option<SortOrder>,
}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.max_results: Option<i32>The maximum number of query logging configurations that you want to return in the response to a ListResolverQueryLogConfigs request. If you don't specify a value for MaxResults, Resolver returns up to 100 query logging configurations.
next_token: Option<String>For the first ListResolverQueryLogConfigs request, omit this value.
If there are more than MaxResults query logging configurations that match the values that you specify for Filters, you can submit another ListResolverQueryLogConfigs request to get the next group of configurations. In the next request, specify the value of NextToken from the previous response.
filters: Option<Vec<Filter>>An optional specification to return a subset of query logging configurations.
If you submit a second or subsequent ListResolverQueryLogConfigs request and specify the NextToken parameter, you must use the same values for Filters, if any, as in the previous request.
sort_by: Option<String>The element that you want Resolver to sort query logging configurations by.
If you submit a second or subsequent ListResolverQueryLogConfigs request and specify the NextToken parameter, you must use the same value for SortBy, if any, as in the previous request.
Valid values include the following elements:
-
Arn: The ARN of the query logging configuration -
AssociationCount: The number of VPCs that are associated with the specified configuration -
CreationTime: The date and time that Resolver returned when the configuration was created -
CreatorRequestId: The value that was specified forCreatorRequestIdwhen the configuration was created -
DestinationArn: The location that logs are sent to -
Id: The ID of the configuration -
Name: The name of the configuration -
OwnerId: The Amazon Web Services account number of the account that created the configuration -
ShareStatus: Whether the configuration is shared with other Amazon Web Services accounts or shared with the current account by another Amazon Web Services account. Sharing is configured through Resource Access Manager (RAM). -
Status: The current status of the configuration. Valid values include the following:-
CREATING: Resolver is creating the query logging configuration. -
CREATED: The query logging configuration was successfully created. Resolver is logging queries that originate in the specified VPC. -
DELETING: Resolver is deleting this query logging configuration. -
FAILED: Resolver either couldn't create or couldn't delete the query logging configuration. Here are two common causes:-
The specified destination (for example, an Amazon S3 bucket) was deleted.
-
Permissions don't allow sending logs to the destination.
-
-
sort_order: Option<SortOrder>If you specified a value for SortBy, the order that you want query logging configurations to be listed in, ASCENDING or DESCENDING.
If you submit a second or subsequent ListResolverQueryLogConfigs request and specify the NextToken parameter, you must use the same value for SortOrder, if any, as in the previous request.
Implementations§
Source§impl ListResolverQueryLogConfigsInput
impl ListResolverQueryLogConfigsInput
Sourcepub fn max_results(&self) -> Option<i32>
pub fn max_results(&self) -> Option<i32>
The maximum number of query logging configurations that you want to return in the response to a ListResolverQueryLogConfigs request. If you don't specify a value for MaxResults, Resolver returns up to 100 query logging configurations.
Sourcepub fn next_token(&self) -> Option<&str>
pub fn next_token(&self) -> Option<&str>
For the first ListResolverQueryLogConfigs request, omit this value.
If there are more than MaxResults query logging configurations that match the values that you specify for Filters, you can submit another ListResolverQueryLogConfigs request to get the next group of configurations. In the next request, specify the value of NextToken from the previous response.
Sourcepub fn filters(&self) -> &[Filter]
pub fn filters(&self) -> &[Filter]
An optional specification to return a subset of query logging configurations.
If you submit a second or subsequent ListResolverQueryLogConfigs request and specify the NextToken parameter, you must use the same values for Filters, if any, as in the previous request.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .filters.is_none().
Sourcepub fn sort_by(&self) -> Option<&str>
pub fn sort_by(&self) -> Option<&str>
The element that you want Resolver to sort query logging configurations by.
If you submit a second or subsequent ListResolverQueryLogConfigs request and specify the NextToken parameter, you must use the same value for SortBy, if any, as in the previous request.
Valid values include the following elements:
-
Arn: The ARN of the query logging configuration -
AssociationCount: The number of VPCs that are associated with the specified configuration -
CreationTime: The date and time that Resolver returned when the configuration was created -
CreatorRequestId: The value that was specified forCreatorRequestIdwhen the configuration was created -
DestinationArn: The location that logs are sent to -
Id: The ID of the configuration -
Name: The name of the configuration -
OwnerId: The Amazon Web Services account number of the account that created the configuration -
ShareStatus: Whether the configuration is shared with other Amazon Web Services accounts or shared with the current account by another Amazon Web Services account. Sharing is configured through Resource Access Manager (RAM). -
Status: The current status of the configuration. Valid values include the following:-
CREATING: Resolver is creating the query logging configuration. -
CREATED: The query logging configuration was successfully created. Resolver is logging queries that originate in the specified VPC. -
DELETING: Resolver is deleting this query logging configuration. -
FAILED: Resolver either couldn't create or couldn't delete the query logging configuration. Here are two common causes:-
The specified destination (for example, an Amazon S3 bucket) was deleted.
-
Permissions don't allow sending logs to the destination.
-
-
Sourcepub fn sort_order(&self) -> Option<&SortOrder>
pub fn sort_order(&self) -> Option<&SortOrder>
If you specified a value for SortBy, the order that you want query logging configurations to be listed in, ASCENDING or DESCENDING.
If you submit a second or subsequent ListResolverQueryLogConfigs request and specify the NextToken parameter, you must use the same value for SortOrder, if any, as in the previous request.
Source§impl ListResolverQueryLogConfigsInput
impl ListResolverQueryLogConfigsInput
Sourcepub fn builder() -> ListResolverQueryLogConfigsInputBuilder
pub fn builder() -> ListResolverQueryLogConfigsInputBuilder
Creates a new builder-style object to manufacture ListResolverQueryLogConfigsInput.
Trait Implementations§
Source§impl Clone for ListResolverQueryLogConfigsInput
impl Clone for ListResolverQueryLogConfigsInput
Source§fn clone(&self) -> ListResolverQueryLogConfigsInput
fn clone(&self) -> ListResolverQueryLogConfigsInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl PartialEq for ListResolverQueryLogConfigsInput
impl PartialEq for ListResolverQueryLogConfigsInput
Source§fn eq(&self, other: &ListResolverQueryLogConfigsInput) -> bool
fn eq(&self, other: &ListResolverQueryLogConfigsInput) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for ListResolverQueryLogConfigsInput
Auto Trait Implementations§
impl Freeze for ListResolverQueryLogConfigsInput
impl RefUnwindSafe for ListResolverQueryLogConfigsInput
impl Send for ListResolverQueryLogConfigsInput
impl Sync for ListResolverQueryLogConfigsInput
impl Unpin for ListResolverQueryLogConfigsInput
impl UnwindSafe for ListResolverQueryLogConfigsInput
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);