#[non_exhaustive]pub struct CountsSummary {
pub components: Option<ResourceCountsSummary>,
pub environments: Option<ResourceCountsSummary>,
pub environment_templates: Option<ResourceCountsSummary>,
pub service_instances: Option<ResourceCountsSummary>,
pub services: Option<ResourceCountsSummary>,
pub service_templates: Option<ResourceCountsSummary>,
pub pipelines: Option<ResourceCountsSummary>,
}
Expand description
Summary counts of each Proton resource type.
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.components: Option<ResourceCountsSummary>
The total number of components in the Amazon Web Services account.
The semantics of the components
field are different from the semantics of results for other infrastructure-provisioning resources. That's because at this time components don't have associated templates, therefore they don't have the concept of staleness. The components
object will only contain total
and failed
members.
environments: Option<ResourceCountsSummary>
The staleness counts for Proton environments in the Amazon Web Services account. The environments
object will only contain total
members.
environment_templates: Option<ResourceCountsSummary>
The total number of environment templates in the Amazon Web Services account. The environmentTemplates
object will only contain total
members.
service_instances: Option<ResourceCountsSummary>
The staleness counts for Proton service instances in the Amazon Web Services account.
services: Option<ResourceCountsSummary>
The staleness counts for Proton services in the Amazon Web Services account.
service_templates: Option<ResourceCountsSummary>
The total number of service templates in the Amazon Web Services account. The serviceTemplates
object will only contain total
members.
pipelines: Option<ResourceCountsSummary>
The staleness counts for Proton pipelines in the Amazon Web Services account.
Implementations§
Source§impl CountsSummary
impl CountsSummary
Sourcepub fn components(&self) -> Option<&ResourceCountsSummary>
pub fn components(&self) -> Option<&ResourceCountsSummary>
The total number of components in the Amazon Web Services account.
The semantics of the components
field are different from the semantics of results for other infrastructure-provisioning resources. That's because at this time components don't have associated templates, therefore they don't have the concept of staleness. The components
object will only contain total
and failed
members.
Sourcepub fn environments(&self) -> Option<&ResourceCountsSummary>
pub fn environments(&self) -> Option<&ResourceCountsSummary>
The staleness counts for Proton environments in the Amazon Web Services account. The environments
object will only contain total
members.
Sourcepub fn environment_templates(&self) -> Option<&ResourceCountsSummary>
pub fn environment_templates(&self) -> Option<&ResourceCountsSummary>
The total number of environment templates in the Amazon Web Services account. The environmentTemplates
object will only contain total
members.
Sourcepub fn service_instances(&self) -> Option<&ResourceCountsSummary>
pub fn service_instances(&self) -> Option<&ResourceCountsSummary>
The staleness counts for Proton service instances in the Amazon Web Services account.
Sourcepub fn services(&self) -> Option<&ResourceCountsSummary>
pub fn services(&self) -> Option<&ResourceCountsSummary>
The staleness counts for Proton services in the Amazon Web Services account.
Sourcepub fn service_templates(&self) -> Option<&ResourceCountsSummary>
pub fn service_templates(&self) -> Option<&ResourceCountsSummary>
The total number of service templates in the Amazon Web Services account. The serviceTemplates
object will only contain total
members.
Sourcepub fn pipelines(&self) -> Option<&ResourceCountsSummary>
pub fn pipelines(&self) -> Option<&ResourceCountsSummary>
The staleness counts for Proton pipelines in the Amazon Web Services account.
Source§impl CountsSummary
impl CountsSummary
Sourcepub fn builder() -> CountsSummaryBuilder
pub fn builder() -> CountsSummaryBuilder
Creates a new builder-style object to manufacture CountsSummary
.
Trait Implementations§
Source§impl Clone for CountsSummary
impl Clone for CountsSummary
Source§fn clone(&self) -> CountsSummary
fn clone(&self) -> CountsSummary
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for CountsSummary
impl Debug for CountsSummary
Source§impl PartialEq for CountsSummary
impl PartialEq for CountsSummary
impl StructuralPartialEq for CountsSummary
Auto Trait Implementations§
impl Freeze for CountsSummary
impl RefUnwindSafe for CountsSummary
impl Send for CountsSummary
impl Sync for CountsSummary
impl Unpin for CountsSummary
impl UnwindSafe for CountsSummary
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);