#[non_exhaustive]pub struct RelationalDatabase {Show 26 fields
pub name: Option<String>,
pub arn: Option<String>,
pub support_code: Option<String>,
pub created_at: Option<DateTime>,
pub location: Option<ResourceLocation>,
pub resource_type: Option<ResourceType>,
pub tags: Option<Vec<Tag>>,
pub relational_database_blueprint_id: Option<String>,
pub relational_database_bundle_id: Option<String>,
pub master_database_name: Option<String>,
pub hardware: Option<RelationalDatabaseHardware>,
pub state: Option<String>,
pub secondary_availability_zone: Option<String>,
pub backup_retention_enabled: Option<bool>,
pub pending_modified_values: Option<PendingModifiedRelationalDatabaseValues>,
pub engine: Option<String>,
pub engine_version: Option<String>,
pub latest_restorable_time: Option<DateTime>,
pub master_username: Option<String>,
pub parameter_apply_status: Option<String>,
pub preferred_backup_window: Option<String>,
pub preferred_maintenance_window: Option<String>,
pub publicly_accessible: Option<bool>,
pub master_endpoint: Option<RelationalDatabaseEndpoint>,
pub pending_maintenance_actions: Option<Vec<PendingMaintenanceAction>>,
pub ca_certificate_identifier: Option<String>,
}Expand description
Describes a database.
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.name: Option<String>The unique name of the database resource in Lightsail.
arn: Option<String>The Amazon Resource Name (ARN) of the database.
support_code: Option<String>The support code for the database. Include this code in your email to support when you have questions about a database in Lightsail. This code enables our support team to look up your Lightsail information more easily.
created_at: Option<DateTime>The timestamp when the database was created. Formatted in Unix time.
location: Option<ResourceLocation>The Region name and Availability Zone where the database is located.
resource_type: Option<ResourceType>The Lightsail resource type for the database (for example, RelationalDatabase).
The tag keys and optional values for the resource. For more information about tags in Lightsail, see the Amazon Lightsail Developer Guide.
relational_database_blueprint_id: Option<String>The blueprint ID for the database. A blueprint describes the major engine version of a database.
relational_database_bundle_id: Option<String>The bundle ID for the database. A bundle describes the performance specifications for your database.
master_database_name: Option<String>The name of the master database created when the Lightsail database resource is created.
hardware: Option<RelationalDatabaseHardware>Describes the hardware of the database.
state: Option<String>Describes the current state of the database.
secondary_availability_zone: Option<String>Describes the secondary Availability Zone of a high availability database.
The secondary database is used for failover support of a high availability database.
backup_retention_enabled: Option<bool>A Boolean value indicating whether automated backup retention is enabled for the database.
pending_modified_values: Option<PendingModifiedRelationalDatabaseValues>Describes pending database value modifications.
engine: Option<String>The database software (for example, MySQL).
engine_version: Option<String>The database engine version (for example, 5.7.23).
latest_restorable_time: Option<DateTime>The latest point in time to which the database can be restored. Formatted in Unix time.
master_username: Option<String>The master user name of the database.
parameter_apply_status: Option<String>The status of parameter updates for the database.
preferred_backup_window: Option<String>The daily time range during which automated backups are created for the database (for example, 16:00-16:30).
preferred_maintenance_window: Option<String>The weekly time range during which system maintenance can occur on the database.
In the format ddd:hh24:mi-ddd:hh24:mi. For example, Tue:17:00-Tue:17:30.
publicly_accessible: Option<bool>A Boolean value indicating whether the database is publicly accessible.
master_endpoint: Option<RelationalDatabaseEndpoint>The master endpoint for the database.
pending_maintenance_actions: Option<Vec<PendingMaintenanceAction>>Describes the pending maintenance actions for the database.
ca_certificate_identifier: Option<String>The certificate associated with the database.
Implementations§
Source§impl RelationalDatabase
impl RelationalDatabase
Sourcepub fn support_code(&self) -> Option<&str>
pub fn support_code(&self) -> Option<&str>
The support code for the database. Include this code in your email to support when you have questions about a database in Lightsail. This code enables our support team to look up your Lightsail information more easily.
Sourcepub fn created_at(&self) -> Option<&DateTime>
pub fn created_at(&self) -> Option<&DateTime>
The timestamp when the database was created. Formatted in Unix time.
Sourcepub fn location(&self) -> Option<&ResourceLocation>
pub fn location(&self) -> Option<&ResourceLocation>
The Region name and Availability Zone where the database is located.
Sourcepub fn resource_type(&self) -> Option<&ResourceType>
pub fn resource_type(&self) -> Option<&ResourceType>
The Lightsail resource type for the database (for example, RelationalDatabase).
The tag keys and optional values for the resource. For more information about tags in Lightsail, see the Amazon Lightsail Developer 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 .tags.is_none().
Sourcepub fn relational_database_blueprint_id(&self) -> Option<&str>
pub fn relational_database_blueprint_id(&self) -> Option<&str>
The blueprint ID for the database. A blueprint describes the major engine version of a database.
Sourcepub fn relational_database_bundle_id(&self) -> Option<&str>
pub fn relational_database_bundle_id(&self) -> Option<&str>
The bundle ID for the database. A bundle describes the performance specifications for your database.
Sourcepub fn master_database_name(&self) -> Option<&str>
pub fn master_database_name(&self) -> Option<&str>
The name of the master database created when the Lightsail database resource is created.
Sourcepub fn hardware(&self) -> Option<&RelationalDatabaseHardware>
pub fn hardware(&self) -> Option<&RelationalDatabaseHardware>
Describes the hardware of the database.
Sourcepub fn secondary_availability_zone(&self) -> Option<&str>
pub fn secondary_availability_zone(&self) -> Option<&str>
Describes the secondary Availability Zone of a high availability database.
The secondary database is used for failover support of a high availability database.
Sourcepub fn backup_retention_enabled(&self) -> Option<bool>
pub fn backup_retention_enabled(&self) -> Option<bool>
A Boolean value indicating whether automated backup retention is enabled for the database.
Sourcepub fn pending_modified_values(
&self,
) -> Option<&PendingModifiedRelationalDatabaseValues>
pub fn pending_modified_values( &self, ) -> Option<&PendingModifiedRelationalDatabaseValues>
Describes pending database value modifications.
Sourcepub fn engine_version(&self) -> Option<&str>
pub fn engine_version(&self) -> Option<&str>
The database engine version (for example, 5.7.23).
Sourcepub fn latest_restorable_time(&self) -> Option<&DateTime>
pub fn latest_restorable_time(&self) -> Option<&DateTime>
The latest point in time to which the database can be restored. Formatted in Unix time.
Sourcepub fn master_username(&self) -> Option<&str>
pub fn master_username(&self) -> Option<&str>
The master user name of the database.
Sourcepub fn parameter_apply_status(&self) -> Option<&str>
pub fn parameter_apply_status(&self) -> Option<&str>
The status of parameter updates for the database.
Sourcepub fn preferred_backup_window(&self) -> Option<&str>
pub fn preferred_backup_window(&self) -> Option<&str>
The daily time range during which automated backups are created for the database (for example, 16:00-16:30).
Sourcepub fn preferred_maintenance_window(&self) -> Option<&str>
pub fn preferred_maintenance_window(&self) -> Option<&str>
The weekly time range during which system maintenance can occur on the database.
In the format ddd:hh24:mi-ddd:hh24:mi. For example, Tue:17:00-Tue:17:30.
Sourcepub fn publicly_accessible(&self) -> Option<bool>
pub fn publicly_accessible(&self) -> Option<bool>
A Boolean value indicating whether the database is publicly accessible.
Sourcepub fn master_endpoint(&self) -> Option<&RelationalDatabaseEndpoint>
pub fn master_endpoint(&self) -> Option<&RelationalDatabaseEndpoint>
The master endpoint for the database.
Sourcepub fn pending_maintenance_actions(&self) -> &[PendingMaintenanceAction]
pub fn pending_maintenance_actions(&self) -> &[PendingMaintenanceAction]
Describes the pending maintenance actions for the database.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .pending_maintenance_actions.is_none().
Sourcepub fn ca_certificate_identifier(&self) -> Option<&str>
pub fn ca_certificate_identifier(&self) -> Option<&str>
The certificate associated with the database.
Source§impl RelationalDatabase
impl RelationalDatabase
Sourcepub fn builder() -> RelationalDatabaseBuilder
pub fn builder() -> RelationalDatabaseBuilder
Creates a new builder-style object to manufacture RelationalDatabase.
Trait Implementations§
Source§impl Clone for RelationalDatabase
impl Clone for RelationalDatabase
Source§fn clone(&self) -> RelationalDatabase
fn clone(&self) -> RelationalDatabase
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for RelationalDatabase
impl Debug for RelationalDatabase
Source§impl PartialEq for RelationalDatabase
impl PartialEq for RelationalDatabase
impl StructuralPartialEq for RelationalDatabase
Auto Trait Implementations§
impl Freeze for RelationalDatabase
impl RefUnwindSafe for RelationalDatabase
impl Send for RelationalDatabase
impl Sync for RelationalDatabase
impl Unpin for RelationalDatabase
impl UnwindSafe for RelationalDatabase
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);