#[non_exhaustive]pub struct ModifyIpamResourceDiscoveryInput {
pub dry_run: Option<bool>,
pub ipam_resource_discovery_id: Option<String>,
pub description: Option<String>,
pub add_operating_regions: Option<Vec<AddIpamOperatingRegion>>,
pub remove_operating_regions: Option<Vec<RemoveIpamOperatingRegion>>,
pub add_organizational_unit_exclusions: Option<Vec<AddIpamOrganizationalUnitExclusion>>,
pub remove_organizational_unit_exclusions: Option<Vec<RemoveIpamOrganizationalUnitExclusion>>,
}
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.dry_run: Option<bool>
A check for whether you have the required permissions for the action without actually making the request and provides an error response. If you have the required permissions, the error response is DryRunOperation
. Otherwise, it is UnauthorizedOperation
.
ipam_resource_discovery_id: Option<String>
A resource discovery ID.
description: Option<String>
A resource discovery description.
add_operating_regions: Option<Vec<AddIpamOperatingRegion>>
Add operating Regions to the resource discovery. Operating Regions are Amazon Web Services Regions where the IPAM is allowed to manage IP address CIDRs. IPAM only discovers and monitors resources in the Amazon Web Services Regions you select as operating Regions.
remove_operating_regions: Option<Vec<RemoveIpamOperatingRegion>>
Remove operating Regions.
add_organizational_unit_exclusions: Option<Vec<AddIpamOrganizationalUnitExclusion>>
Add an Organizational Unit (OU) exclusion to your IPAM. If your IPAM is integrated with Amazon Web Services Organizations and you add an organizational unit (OU) exclusion, IPAM will not manage the IP addresses in accounts in that OU exclusion. There is a limit on the number of exclusions you can create. For more information, see Quotas for your IPAM in the Amazon VPC IPAM User Guide.
The resulting set of exclusions must not result in "overlap", meaning two or more OU exclusions must not exclude the same OU. For more information and examples, see the Amazon Web Services CLI request process in Add or remove OU exclusions in the Amazon VPC User Guide.
remove_organizational_unit_exclusions: Option<Vec<RemoveIpamOrganizationalUnitExclusion>>
Remove an Organizational Unit (OU) exclusion to your IPAM. If your IPAM is integrated with Amazon Web Services Organizations and you add an organizational unit (OU) exclusion, IPAM will not manage the IP addresses in accounts in that OU exclusion. There is a limit on the number of exclusions you can create. For more information, see Quotas for your IPAM in the Amazon VPC IPAM User Guide.
The resulting set of exclusions must not result in "overlap", meaning two or more OU exclusions must not exclude the same OU. For more information and examples, see the Amazon Web Services CLI request process in Add or remove OU exclusions in the Amazon VPC User Guide.
Implementations§
Source§impl ModifyIpamResourceDiscoveryInput
impl ModifyIpamResourceDiscoveryInput
Sourcepub fn dry_run(&self) -> Option<bool>
pub fn dry_run(&self) -> Option<bool>
A check for whether you have the required permissions for the action without actually making the request and provides an error response. If you have the required permissions, the error response is DryRunOperation
. Otherwise, it is UnauthorizedOperation
.
Sourcepub fn ipam_resource_discovery_id(&self) -> Option<&str>
pub fn ipam_resource_discovery_id(&self) -> Option<&str>
A resource discovery ID.
Sourcepub fn description(&self) -> Option<&str>
pub fn description(&self) -> Option<&str>
A resource discovery description.
Sourcepub fn add_operating_regions(&self) -> &[AddIpamOperatingRegion]
pub fn add_operating_regions(&self) -> &[AddIpamOperatingRegion]
Add operating Regions to the resource discovery. Operating Regions are Amazon Web Services Regions where the IPAM is allowed to manage IP address CIDRs. IPAM only discovers and monitors resources in the Amazon Web Services Regions you select as operating Regions.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .add_operating_regions.is_none()
.
Sourcepub fn remove_operating_regions(&self) -> &[RemoveIpamOperatingRegion]
pub fn remove_operating_regions(&self) -> &[RemoveIpamOperatingRegion]
Remove operating Regions.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .remove_operating_regions.is_none()
.
Sourcepub fn add_organizational_unit_exclusions(
&self,
) -> &[AddIpamOrganizationalUnitExclusion]
pub fn add_organizational_unit_exclusions( &self, ) -> &[AddIpamOrganizationalUnitExclusion]
Add an Organizational Unit (OU) exclusion to your IPAM. If your IPAM is integrated with Amazon Web Services Organizations and you add an organizational unit (OU) exclusion, IPAM will not manage the IP addresses in accounts in that OU exclusion. There is a limit on the number of exclusions you can create. For more information, see Quotas for your IPAM in the Amazon VPC IPAM User Guide.
The resulting set of exclusions must not result in "overlap", meaning two or more OU exclusions must not exclude the same OU. For more information and examples, see the Amazon Web Services CLI request process in Add or remove OU exclusions in the Amazon VPC User Guide.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .add_organizational_unit_exclusions.is_none()
.
Sourcepub fn remove_organizational_unit_exclusions(
&self,
) -> &[RemoveIpamOrganizationalUnitExclusion]
pub fn remove_organizational_unit_exclusions( &self, ) -> &[RemoveIpamOrganizationalUnitExclusion]
Remove an Organizational Unit (OU) exclusion to your IPAM. If your IPAM is integrated with Amazon Web Services Organizations and you add an organizational unit (OU) exclusion, IPAM will not manage the IP addresses in accounts in that OU exclusion. There is a limit on the number of exclusions you can create. For more information, see Quotas for your IPAM in the Amazon VPC IPAM User Guide.
The resulting set of exclusions must not result in "overlap", meaning two or more OU exclusions must not exclude the same OU. For more information and examples, see the Amazon Web Services CLI request process in Add or remove OU exclusions in the Amazon VPC User Guide.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .remove_organizational_unit_exclusions.is_none()
.
Source§impl ModifyIpamResourceDiscoveryInput
impl ModifyIpamResourceDiscoveryInput
Sourcepub fn builder() -> ModifyIpamResourceDiscoveryInputBuilder
pub fn builder() -> ModifyIpamResourceDiscoveryInputBuilder
Creates a new builder-style object to manufacture ModifyIpamResourceDiscoveryInput
.
Trait Implementations§
Source§impl Clone for ModifyIpamResourceDiscoveryInput
impl Clone for ModifyIpamResourceDiscoveryInput
Source§fn clone(&self) -> ModifyIpamResourceDiscoveryInput
fn clone(&self) -> ModifyIpamResourceDiscoveryInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for ModifyIpamResourceDiscoveryInput
impl PartialEq for ModifyIpamResourceDiscoveryInput
Source§fn eq(&self, other: &ModifyIpamResourceDiscoveryInput) -> bool
fn eq(&self, other: &ModifyIpamResourceDiscoveryInput) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for ModifyIpamResourceDiscoveryInput
Auto Trait Implementations§
impl Freeze for ModifyIpamResourceDiscoveryInput
impl RefUnwindSafe for ModifyIpamResourceDiscoveryInput
impl Send for ModifyIpamResourceDiscoveryInput
impl Sync for ModifyIpamResourceDiscoveryInput
impl Unpin for ModifyIpamResourceDiscoveryInput
impl UnwindSafe for ModifyIpamResourceDiscoveryInput
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);