#[non_exhaustive]pub struct CreateDbClusterInput {Show 18 fields
pub name: Option<String>,
pub username: Option<String>,
pub password: Option<String>,
pub organization: Option<String>,
pub bucket: Option<String>,
pub port: Option<i32>,
pub db_parameter_group_identifier: Option<String>,
pub db_instance_type: Option<DbInstanceType>,
pub db_storage_type: Option<DbStorageType>,
pub allocated_storage: Option<i32>,
pub network_type: Option<NetworkType>,
pub publicly_accessible: Option<bool>,
pub vpc_subnet_ids: Option<Vec<String>>,
pub vpc_security_group_ids: Option<Vec<String>>,
pub deployment_type: Option<ClusterDeploymentType>,
pub failover_mode: Option<FailoverMode>,
pub log_delivery_configuration: Option<LogDeliveryConfiguration>,
pub tags: Option<HashMap<String, String>>,
}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 name that uniquely identifies the DB cluster when interacting with the Amazon Timestream for InfluxDB API and CLI commands. This name will also be a prefix included in the endpoint. DB cluster names must be unique per customer and per region.
username: Option<String>The username of the initial admin user created in InfluxDB. Must start with a letter and can't end with a hyphen or contain two consecutive hyphens. For example, my-user1. This username will allow you to access the InfluxDB UI to perform various administrative tasks and also use the InfluxDB CLI to create an operator token. These attributes will be stored in a secret created in Secrets Manager in your account.
password: Option<String>The password of the initial admin user created in InfluxDB. This password will allow you to access the InfluxDB UI to perform various administrative tasks and also use the InfluxDB CLI to create an operator token. These attributes will be stored in a secret created in Secrets Manager in your account.
organization: Option<String>The name of the initial organization for the initial admin user in InfluxDB. An InfluxDB organization is a workspace for a group of users.
bucket: Option<String>The name of the initial InfluxDB bucket. All InfluxDB data is stored in a bucket. A bucket combines the concept of a database and a retention period (the duration of time that each data point persists). A bucket belongs to an organization.
port: Option<i32>The port number on which InfluxDB accepts connections.
Valid Values: 1024-65535
Default: 8086
Constraints: The value can't be 2375-2376, 7788-7799, 8090, or 51678-51680
db_parameter_group_identifier: Option<String>The ID of the DB parameter group to assign to your DB cluster. DB parameter groups specify how the database is configured. For example, DB parameter groups can specify the limit for query concurrency.
db_instance_type: Option<DbInstanceType>The Timestream for InfluxDB DB instance type to run InfluxDB on.
db_storage_type: Option<DbStorageType>The Timestream for InfluxDB DB storage type to read and write InfluxDB data.
You can choose between three different types of provisioned Influx IOPS Included storage according to your workload requirements:
-
Influx I/O Included 3000 IOPS
-
Influx I/O Included 12000 IOPS
-
Influx I/O Included 16000 IOPS
allocated_storage: Option<i32>The amount of storage to allocate for your DB storage type in GiB (gibibytes).
network_type: Option<NetworkType>Specifies whether the network type of the Timestream for InfluxDB cluster is IPv4, which can communicate over IPv4 protocol only, or DUAL, which can communicate over both IPv4 and IPv6 protocols.
publicly_accessible: Option<bool>Configures the Timestream for InfluxDB cluster with a public IP to facilitate access from outside the VPC.
vpc_subnet_ids: Option<Vec<String>>A list of VPC subnet IDs to associate with the DB cluster. Provide at least two VPC subnet IDs in different Availability Zones when deploying with a Multi-AZ standby.
vpc_security_group_ids: Option<Vec<String>>A list of VPC security group IDs to associate with the Timestream for InfluxDB cluster.
deployment_type: Option<ClusterDeploymentType>Specifies the type of cluster to create.
failover_mode: Option<FailoverMode>Specifies the behavior of failure recovery when the primary node of the cluster fails.
log_delivery_configuration: Option<LogDeliveryConfiguration>Configuration for sending InfluxDB engine logs to a specified S3 bucket.
A list of key-value pairs to associate with the DB instance.
Implementations§
Source§impl CreateDbClusterInput
impl CreateDbClusterInput
Sourcepub fn name(&self) -> Option<&str>
pub fn name(&self) -> Option<&str>
The name that uniquely identifies the DB cluster when interacting with the Amazon Timestream for InfluxDB API and CLI commands. This name will also be a prefix included in the endpoint. DB cluster names must be unique per customer and per region.
Sourcepub fn username(&self) -> Option<&str>
pub fn username(&self) -> Option<&str>
The username of the initial admin user created in InfluxDB. Must start with a letter and can't end with a hyphen or contain two consecutive hyphens. For example, my-user1. This username will allow you to access the InfluxDB UI to perform various administrative tasks and also use the InfluxDB CLI to create an operator token. These attributes will be stored in a secret created in Secrets Manager in your account.
Sourcepub fn password(&self) -> Option<&str>
pub fn password(&self) -> Option<&str>
The password of the initial admin user created in InfluxDB. This password will allow you to access the InfluxDB UI to perform various administrative tasks and also use the InfluxDB CLI to create an operator token. These attributes will be stored in a secret created in Secrets Manager in your account.
Sourcepub fn organization(&self) -> Option<&str>
pub fn organization(&self) -> Option<&str>
The name of the initial organization for the initial admin user in InfluxDB. An InfluxDB organization is a workspace for a group of users.
Sourcepub fn bucket(&self) -> Option<&str>
pub fn bucket(&self) -> Option<&str>
The name of the initial InfluxDB bucket. All InfluxDB data is stored in a bucket. A bucket combines the concept of a database and a retention period (the duration of time that each data point persists). A bucket belongs to an organization.
Sourcepub fn port(&self) -> Option<i32>
pub fn port(&self) -> Option<i32>
The port number on which InfluxDB accepts connections.
Valid Values: 1024-65535
Default: 8086
Constraints: The value can't be 2375-2376, 7788-7799, 8090, or 51678-51680
Sourcepub fn db_parameter_group_identifier(&self) -> Option<&str>
pub fn db_parameter_group_identifier(&self) -> Option<&str>
The ID of the DB parameter group to assign to your DB cluster. DB parameter groups specify how the database is configured. For example, DB parameter groups can specify the limit for query concurrency.
Sourcepub fn db_instance_type(&self) -> Option<&DbInstanceType>
pub fn db_instance_type(&self) -> Option<&DbInstanceType>
The Timestream for InfluxDB DB instance type to run InfluxDB on.
Sourcepub fn db_storage_type(&self) -> Option<&DbStorageType>
pub fn db_storage_type(&self) -> Option<&DbStorageType>
The Timestream for InfluxDB DB storage type to read and write InfluxDB data.
You can choose between three different types of provisioned Influx IOPS Included storage according to your workload requirements:
-
Influx I/O Included 3000 IOPS
-
Influx I/O Included 12000 IOPS
-
Influx I/O Included 16000 IOPS
Sourcepub fn allocated_storage(&self) -> Option<i32>
pub fn allocated_storage(&self) -> Option<i32>
The amount of storage to allocate for your DB storage type in GiB (gibibytes).
Sourcepub fn network_type(&self) -> Option<&NetworkType>
pub fn network_type(&self) -> Option<&NetworkType>
Specifies whether the network type of the Timestream for InfluxDB cluster is IPv4, which can communicate over IPv4 protocol only, or DUAL, which can communicate over both IPv4 and IPv6 protocols.
Sourcepub fn publicly_accessible(&self) -> Option<bool>
pub fn publicly_accessible(&self) -> Option<bool>
Configures the Timestream for InfluxDB cluster with a public IP to facilitate access from outside the VPC.
Sourcepub fn vpc_subnet_ids(&self) -> &[String]
pub fn vpc_subnet_ids(&self) -> &[String]
A list of VPC subnet IDs to associate with the DB cluster. Provide at least two VPC subnet IDs in different Availability Zones when deploying with a Multi-AZ standby.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .vpc_subnet_ids.is_none().
Sourcepub fn vpc_security_group_ids(&self) -> &[String]
pub fn vpc_security_group_ids(&self) -> &[String]
A list of VPC security group IDs to associate with the Timestream for InfluxDB cluster.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .vpc_security_group_ids.is_none().
Sourcepub fn deployment_type(&self) -> Option<&ClusterDeploymentType>
pub fn deployment_type(&self) -> Option<&ClusterDeploymentType>
Specifies the type of cluster to create.
Sourcepub fn failover_mode(&self) -> Option<&FailoverMode>
pub fn failover_mode(&self) -> Option<&FailoverMode>
Specifies the behavior of failure recovery when the primary node of the cluster fails.
Sourcepub fn log_delivery_configuration(&self) -> Option<&LogDeliveryConfiguration>
pub fn log_delivery_configuration(&self) -> Option<&LogDeliveryConfiguration>
Configuration for sending InfluxDB engine logs to a specified S3 bucket.
A list of key-value pairs to associate with the DB instance.
Source§impl CreateDbClusterInput
impl CreateDbClusterInput
Sourcepub fn builder() -> CreateDbClusterInputBuilder
pub fn builder() -> CreateDbClusterInputBuilder
Creates a new builder-style object to manufacture CreateDbClusterInput.
Trait Implementations§
Source§impl Clone for CreateDbClusterInput
impl Clone for CreateDbClusterInput
Source§fn clone(&self) -> CreateDbClusterInput
fn clone(&self) -> CreateDbClusterInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for CreateDbClusterInput
impl Debug for CreateDbClusterInput
Source§impl PartialEq for CreateDbClusterInput
impl PartialEq for CreateDbClusterInput
impl StructuralPartialEq for CreateDbClusterInput
Auto Trait Implementations§
impl Freeze for CreateDbClusterInput
impl RefUnwindSafe for CreateDbClusterInput
impl Send for CreateDbClusterInput
impl Sync for CreateDbClusterInput
impl Unpin for CreateDbClusterInput
impl UnwindSafe for CreateDbClusterInput
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);