#[non_exhaustive]pub struct DomainAssociation {
pub domain_association_arn: String,
pub domain_name: String,
pub enable_auto_sub_domain: bool,
pub auto_sub_domain_creation_patterns: Option<Vec<String>>,
pub auto_sub_domain_iam_role: Option<String>,
pub domain_status: DomainStatus,
pub update_status: Option<UpdateStatus>,
pub status_reason: String,
pub certificate_verification_dns_record: Option<String>,
pub sub_domains: Vec<SubDomain>,
pub certificate: Option<Certificate>,
}Expand description
Describes the association between a custom domain and an Amplify app.
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.domain_association_arn: StringThe Amazon Resource Name (ARN) for the domain association.
domain_name: StringThe name of the domain.
enable_auto_sub_domain: boolEnables the automated creation of subdomains for branches.
auto_sub_domain_creation_patterns: Option<Vec<String>>Sets branch patterns for automatic subdomain creation.
auto_sub_domain_iam_role: Option<String>The required AWS Identity and Access Management (IAM) service role for the Amazon Resource Name (ARN) for automatically creating subdomains.
domain_status: DomainStatusThe current status of the domain association.
update_status: Option<UpdateStatus>The status of the domain update operation that is currently in progress. The following list describes the valid update states.
- REQUESTING_CERTIFICATE
-
The certificate is in the process of being updated.
- PENDING_VERIFICATION
-
Indicates that an Amplify managed certificate is in the process of being verified. This occurs during the creation of a custom domain or when a custom domain is updated to use a managed certificate.
- IMPORTING_CUSTOM_CERTIFICATE
-
Indicates that an Amplify custom certificate is in the process of being imported. This occurs during the creation of a custom domain or when a custom domain is updated to use a custom certificate.
- PENDING_DEPLOYMENT
-
Indicates that the subdomain or certificate changes are being propagated.
- AWAITING_APP_CNAME
-
Amplify is waiting for CNAME records corresponding to subdomains to be propagated. If your custom domain is on Route 53, Amplify handles this for you automatically. For more information about custom domains, see Setting up custom domains in the Amplify Hosting User Guide.
- UPDATE_COMPLETE
-
The certificate has been associated with a domain.
- UPDATE_FAILED
-
The certificate has failed to be provisioned or associated, and there is no existing active certificate to roll back to.
status_reason: StringAdditional information that describes why the domain association is in the current state.
certificate_verification_dns_record: Option<String>The DNS record for certificate verification.
sub_domains: Vec<SubDomain>The subdomains for the domain association.
certificate: Option<Certificate>Describes the SSL/TLS certificate for the domain association. This can be your own custom certificate or the default certificate that Amplify provisions for you.
If you are updating your domain to use a different certificate, certificate points to the new certificate that is being created instead of the current active certificate. Otherwise, certificate points to the current active certificate.
Implementations§
Source§impl DomainAssociation
impl DomainAssociation
Sourcepub fn domain_association_arn(&self) -> &str
pub fn domain_association_arn(&self) -> &str
The Amazon Resource Name (ARN) for the domain association.
Sourcepub fn domain_name(&self) -> &str
pub fn domain_name(&self) -> &str
The name of the domain.
Sourcepub fn enable_auto_sub_domain(&self) -> bool
pub fn enable_auto_sub_domain(&self) -> bool
Enables the automated creation of subdomains for branches.
Sourcepub fn auto_sub_domain_creation_patterns(&self) -> &[String]
pub fn auto_sub_domain_creation_patterns(&self) -> &[String]
Sets branch patterns for automatic subdomain creation.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .auto_sub_domain_creation_patterns.is_none().
Sourcepub fn auto_sub_domain_iam_role(&self) -> Option<&str>
pub fn auto_sub_domain_iam_role(&self) -> Option<&str>
The required AWS Identity and Access Management (IAM) service role for the Amazon Resource Name (ARN) for automatically creating subdomains.
Sourcepub fn domain_status(&self) -> &DomainStatus
pub fn domain_status(&self) -> &DomainStatus
The current status of the domain association.
Sourcepub fn update_status(&self) -> Option<&UpdateStatus>
pub fn update_status(&self) -> Option<&UpdateStatus>
The status of the domain update operation that is currently in progress. The following list describes the valid update states.
- REQUESTING_CERTIFICATE
-
The certificate is in the process of being updated.
- PENDING_VERIFICATION
-
Indicates that an Amplify managed certificate is in the process of being verified. This occurs during the creation of a custom domain or when a custom domain is updated to use a managed certificate.
- IMPORTING_CUSTOM_CERTIFICATE
-
Indicates that an Amplify custom certificate is in the process of being imported. This occurs during the creation of a custom domain or when a custom domain is updated to use a custom certificate.
- PENDING_DEPLOYMENT
-
Indicates that the subdomain or certificate changes are being propagated.
- AWAITING_APP_CNAME
-
Amplify is waiting for CNAME records corresponding to subdomains to be propagated. If your custom domain is on Route 53, Amplify handles this for you automatically. For more information about custom domains, see Setting up custom domains in the Amplify Hosting User Guide.
- UPDATE_COMPLETE
-
The certificate has been associated with a domain.
- UPDATE_FAILED
-
The certificate has failed to be provisioned or associated, and there is no existing active certificate to roll back to.
Sourcepub fn status_reason(&self) -> &str
pub fn status_reason(&self) -> &str
Additional information that describes why the domain association is in the current state.
Sourcepub fn certificate_verification_dns_record(&self) -> Option<&str>
pub fn certificate_verification_dns_record(&self) -> Option<&str>
The DNS record for certificate verification.
Sourcepub fn sub_domains(&self) -> &[SubDomain]
pub fn sub_domains(&self) -> &[SubDomain]
The subdomains for the domain association.
Sourcepub fn certificate(&self) -> Option<&Certificate>
pub fn certificate(&self) -> Option<&Certificate>
Describes the SSL/TLS certificate for the domain association. This can be your own custom certificate or the default certificate that Amplify provisions for you.
If you are updating your domain to use a different certificate, certificate points to the new certificate that is being created instead of the current active certificate. Otherwise, certificate points to the current active certificate.
Source§impl DomainAssociation
impl DomainAssociation
Sourcepub fn builder() -> DomainAssociationBuilder
pub fn builder() -> DomainAssociationBuilder
Creates a new builder-style object to manufacture DomainAssociation.
Trait Implementations§
Source§impl Clone for DomainAssociation
impl Clone for DomainAssociation
Source§fn clone(&self) -> DomainAssociation
fn clone(&self) -> DomainAssociation
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for DomainAssociation
impl Debug for DomainAssociation
Source§impl PartialEq for DomainAssociation
impl PartialEq for DomainAssociation
impl StructuralPartialEq for DomainAssociation
Auto Trait Implementations§
impl Freeze for DomainAssociation
impl RefUnwindSafe for DomainAssociation
impl Send for DomainAssociation
impl Sync for DomainAssociation
impl Unpin for DomainAssociation
impl UnwindSafe for DomainAssociation
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);