#[non_exhaustive]pub struct CreateClusterInput {Show 39 fields
pub db_name: Option<String>,
pub cluster_identifier: Option<String>,
pub cluster_type: Option<String>,
pub node_type: Option<String>,
pub master_username: Option<String>,
pub master_user_password: Option<String>,
pub cluster_security_groups: Option<Vec<String>>,
pub vpc_security_group_ids: Option<Vec<String>>,
pub cluster_subnet_group_name: Option<String>,
pub availability_zone: Option<String>,
pub preferred_maintenance_window: Option<String>,
pub cluster_parameter_group_name: Option<String>,
pub automated_snapshot_retention_period: Option<i32>,
pub manual_snapshot_retention_period: Option<i32>,
pub port: Option<i32>,
pub cluster_version: Option<String>,
pub allow_version_upgrade: Option<bool>,
pub number_of_nodes: Option<i32>,
pub publicly_accessible: Option<bool>,
pub encrypted: Option<bool>,
pub hsm_client_certificate_identifier: Option<String>,
pub hsm_configuration_identifier: Option<String>,
pub elastic_ip: Option<String>,
pub tags: Option<Vec<Tag>>,
pub kms_key_id: Option<String>,
pub enhanced_vpc_routing: Option<bool>,
pub additional_info: Option<String>,
pub iam_roles: Option<Vec<String>>,
pub maintenance_track_name: Option<String>,
pub snapshot_schedule_identifier: Option<String>,
pub availability_zone_relocation: Option<bool>,
pub aqua_configuration_status: Option<AquaConfigurationStatus>,
pub default_iam_role_arn: Option<String>,
pub load_sample_data: Option<String>,
pub manage_master_password: Option<bool>,
pub master_password_secret_kms_key_id: Option<String>,
pub ip_address_type: Option<String>,
pub multi_az: Option<bool>,
pub redshift_idc_application_arn: Option<String>,
}
Expand description
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.db_name: Option<String>
The name of the first database to be created when the cluster is created.
To create additional databases after the cluster is created, connect to the cluster with a SQL client and use SQL commands to create a database. For more information, go to Create a Database in the Amazon Redshift Database Developer Guide.
Default: dev
Constraints:
-
Must contain 1 to 64 alphanumeric characters.
-
Must contain only lowercase letters.
-
Cannot be a word that is reserved by the service. A list of reserved words can be found in Reserved Words in the Amazon Redshift Database Developer Guide.
cluster_identifier: Option<String>
A unique identifier for the cluster. You use this identifier to refer to the cluster for any subsequent cluster operations such as deleting or modifying. The identifier also appears in the Amazon Redshift console.
Constraints:
-
Must contain from 1 to 63 alphanumeric characters or hyphens.
-
Alphabetic characters must be lowercase.
-
First character must be a letter.
-
Cannot end with a hyphen or contain two consecutive hyphens.
-
Must be unique for all clusters within an Amazon Web Services account.
Example: myexamplecluster
cluster_type: Option<String>
The type of the cluster. When cluster type is specified as
-
single-node
, the NumberOfNodes parameter is not required. -
multi-node
, the NumberOfNodes parameter is required.
Valid Values: multi-node
| single-node
Default: multi-node
node_type: Option<String>
The node type to be provisioned for the cluster. For information about node types, go to Working with Clusters in the Amazon Redshift Cluster Management Guide.
Valid Values: dc2.large
| dc2.8xlarge
| ra3.large
| ra3.xlplus
| ra3.4xlarge
| ra3.16xlarge
master_username: Option<String>
The user name associated with the admin user account for the cluster that is being created.
Constraints:
-
Must be 1 - 128 alphanumeric characters or hyphens. The user name can't be
PUBLIC
. -
Must contain only lowercase letters, numbers, underscore, plus sign, period (dot), at symbol (@), or hyphen.
-
The first character must be a letter.
-
Must not contain a colon (:) or a slash (/).
-
Cannot be a reserved word. A list of reserved words can be found in Reserved Words in the Amazon Redshift Database Developer Guide.
master_user_password: Option<String>
The password associated with the admin user account for the cluster that is being created.
You can't use MasterUserPassword
if ManageMasterPassword
is true
.
Constraints:
-
Must be between 8 and 64 characters in length.
-
Must contain at least one uppercase letter.
-
Must contain at least one lowercase letter.
-
Must contain one number.
-
Can be any printable ASCII character (ASCII code 33-126) except
'
(single quote),"
(double quote),\
,/
, or@
.
cluster_security_groups: Option<Vec<String>>
A list of security groups to be associated with this cluster.
Default: The default cluster security group for Amazon Redshift.
vpc_security_group_ids: Option<Vec<String>>
A list of Virtual Private Cloud (VPC) security groups to be associated with the cluster.
Default: The default VPC security group is associated with the cluster.
cluster_subnet_group_name: Option<String>
The name of a cluster subnet group to be associated with this cluster.
If this parameter is not provided the resulting cluster will be deployed outside virtual private cloud (VPC).
availability_zone: Option<String>
The EC2 Availability Zone (AZ) in which you want Amazon Redshift to provision the cluster. For example, if you have several EC2 instances running in a specific Availability Zone, then you might want the cluster to be provisioned in the same zone in order to decrease network latency.
Default: A random, system-chosen Availability Zone in the region that is specified by the endpoint.
Example: us-east-2d
Constraint: The specified Availability Zone must be in the same region as the current endpoint.
preferred_maintenance_window: Option<String>
The weekly time range (in UTC) during which automated cluster maintenance can occur.
Format: ddd:hh24:mi-ddd:hh24:mi
Default: A 30-minute window selected at random from an 8-hour block of time per region, occurring on a random day of the week. For more information about the time blocks for each region, see Maintenance Windows in Amazon Redshift Cluster Management Guide.
Valid Days: Mon | Tue | Wed | Thu | Fri | Sat | Sun
Constraints: Minimum 30-minute window.
cluster_parameter_group_name: Option<String>
The name of the parameter group to be associated with this cluster.
Default: The default Amazon Redshift cluster parameter group. For information about the default parameter group, go to Working with Amazon Redshift Parameter Groups
Constraints:
-
Must be 1 to 255 alphanumeric characters or hyphens.
-
First character must be a letter.
-
Cannot end with a hyphen or contain two consecutive hyphens.
automated_snapshot_retention_period: Option<i32>
The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with CreateClusterSnapshot
.
You can't disable automated snapshots for RA3 node types. Set the automated retention period from 1-35 days.
Default: 1
Constraints: Must be a value from 0 to 35.
manual_snapshot_retention_period: Option<i32>
The default number of days to retain a manual snapshot. If the value is -1, the snapshot is retained indefinitely. This setting doesn't change the retention period of existing snapshots.
The value must be either -1 or an integer between 1 and 3,653.
port: Option<i32>
The port number on which the cluster accepts incoming connections.
The cluster is accessible only via the JDBC and ODBC connection strings. Part of the connection string requires the port on which the cluster will listen for incoming connections.
Default: 5439
Valid Values:
-
For clusters with ra3 nodes - Select a port within the ranges
5431-5455
or8191-8215
. (If you have an existing cluster with ra3 nodes, it isn't required that you change the port to these ranges.) -
For clusters with dc2 nodes - Select a port within the range
1150-65535
.
cluster_version: Option<String>
The version of the Amazon Redshift engine software that you want to deploy on the cluster.
The version selected runs on all the nodes in the cluster.
Constraints: Only version 1.0 is currently available.
Example: 1.0
allow_version_upgrade: Option<bool>
If true
, major version upgrades can be applied during the maintenance window to the Amazon Redshift engine that is running on the cluster.
When a new major version of the Amazon Redshift engine is released, you can request that the service automatically apply upgrades during the maintenance window to the Amazon Redshift engine that is running on your cluster.
Default: true
number_of_nodes: Option<i32>
The number of compute nodes in the cluster. This parameter is required when the ClusterType parameter is specified as multi-node
.
For information about determining how many nodes you need, go to Working with Clusters in the Amazon Redshift Cluster Management Guide.
If you don't specify this parameter, you get a single-node cluster. When requesting a multi-node cluster, you must specify the number of nodes that you want in the cluster.
Default: 1
Constraints: Value must be at least 1 and no more than 100.
publicly_accessible: Option<bool>
If true
, the cluster can be accessed from a public network.
Default: false
encrypted: Option<bool>
If true
, the data in the cluster is encrypted at rest. If you set the value on this parameter to false
, the request will fail.
Default: true
hsm_client_certificate_identifier: Option<String>
Specifies the name of the HSM client certificate the Amazon Redshift cluster uses to retrieve the data encryption keys stored in an HSM.
hsm_configuration_identifier: Option<String>
Specifies the name of the HSM configuration that contains the information the Amazon Redshift cluster can use to retrieve and store keys in an HSM.
elastic_ip: Option<String>
The Elastic IP (EIP) address for the cluster.
Constraints: The cluster must be provisioned in EC2-VPC and publicly-accessible through an Internet gateway. Don't specify the Elastic IP address for a publicly accessible cluster with availability zone relocation turned on. For more information about provisioning clusters in EC2-VPC, go to Supported Platforms to Launch Your Cluster in the Amazon Redshift Cluster Management Guide.
A list of tag instances.
kms_key_id: Option<String>
The Key Management Service (KMS) key ID of the encryption key that you want to use to encrypt data in the cluster.
enhanced_vpc_routing: Option<bool>
An option that specifies whether to create the cluster with enhanced VPC routing enabled. To create a cluster that uses enhanced VPC routing, the cluster must be in a VPC. For more information, see Enhanced VPC Routing in the Amazon Redshift Cluster Management Guide.
If this option is true
, enhanced VPC routing is enabled.
Default: false
additional_info: Option<String>
Reserved.
iam_roles: Option<Vec<String>>
A list of Identity and Access Management (IAM) roles that can be used by the cluster to access other Amazon Web Services services. You must supply the IAM roles in their Amazon Resource Name (ARN) format.
The maximum number of IAM roles that you can associate is subject to a quota. For more information, go to Quotas and limits in the Amazon Redshift Cluster Management Guide.
maintenance_track_name: Option<String>
An optional parameter for the name of the maintenance track for the cluster. If you don't provide a maintenance track name, the cluster is assigned to the current
track.
snapshot_schedule_identifier: Option<String>
A unique identifier for the snapshot schedule.
availability_zone_relocation: Option<bool>
The option to enable relocation for an Amazon Redshift cluster between Availability Zones after the cluster is created.
aqua_configuration_status: Option<AquaConfigurationStatus>
This parameter is retired. It does not set the AQUA configuration status. Amazon Redshift automatically determines whether to use AQUA (Advanced Query Accelerator).
default_iam_role_arn: Option<String>
The Amazon Resource Name (ARN) for the IAM role that was set as default for the cluster when the cluster was created.
load_sample_data: Option<String>
A flag that specifies whether to load sample data once the cluster is created.
manage_master_password: Option<bool>
If true
, Amazon Redshift uses Secrets Manager to manage this cluster's admin credentials. You can't use MasterUserPassword
if ManageMasterPassword
is true. If ManageMasterPassword
is false or not set, Amazon Redshift uses MasterUserPassword
for the admin user account's password.
master_password_secret_kms_key_id: Option<String>
The ID of the Key Management Service (KMS) key used to encrypt and store the cluster's admin credentials secret. You can only use this parameter if ManageMasterPassword
is true.
ip_address_type: Option<String>
The IP address types that the cluster supports. Possible values are ipv4
and dualstack
.
multi_az: Option<bool>
If true, Amazon Redshift will deploy the cluster in two Availability Zones (AZ).
redshift_idc_application_arn: Option<String>
The Amazon resource name (ARN) of the Amazon Redshift IAM Identity Center application.
Implementations§
Source§impl CreateClusterInput
impl CreateClusterInput
Sourcepub fn db_name(&self) -> Option<&str>
pub fn db_name(&self) -> Option<&str>
The name of the first database to be created when the cluster is created.
To create additional databases after the cluster is created, connect to the cluster with a SQL client and use SQL commands to create a database. For more information, go to Create a Database in the Amazon Redshift Database Developer Guide.
Default: dev
Constraints:
-
Must contain 1 to 64 alphanumeric characters.
-
Must contain only lowercase letters.
-
Cannot be a word that is reserved by the service. A list of reserved words can be found in Reserved Words in the Amazon Redshift Database Developer Guide.
Sourcepub fn cluster_identifier(&self) -> Option<&str>
pub fn cluster_identifier(&self) -> Option<&str>
A unique identifier for the cluster. You use this identifier to refer to the cluster for any subsequent cluster operations such as deleting or modifying. The identifier also appears in the Amazon Redshift console.
Constraints:
-
Must contain from 1 to 63 alphanumeric characters or hyphens.
-
Alphabetic characters must be lowercase.
-
First character must be a letter.
-
Cannot end with a hyphen or contain two consecutive hyphens.
-
Must be unique for all clusters within an Amazon Web Services account.
Example: myexamplecluster
Sourcepub fn cluster_type(&self) -> Option<&str>
pub fn cluster_type(&self) -> Option<&str>
The type of the cluster. When cluster type is specified as
-
single-node
, the NumberOfNodes parameter is not required. -
multi-node
, the NumberOfNodes parameter is required.
Valid Values: multi-node
| single-node
Default: multi-node
Sourcepub fn node_type(&self) -> Option<&str>
pub fn node_type(&self) -> Option<&str>
The node type to be provisioned for the cluster. For information about node types, go to Working with Clusters in the Amazon Redshift Cluster Management Guide.
Valid Values: dc2.large
| dc2.8xlarge
| ra3.large
| ra3.xlplus
| ra3.4xlarge
| ra3.16xlarge
Sourcepub fn master_username(&self) -> Option<&str>
pub fn master_username(&self) -> Option<&str>
The user name associated with the admin user account for the cluster that is being created.
Constraints:
-
Must be 1 - 128 alphanumeric characters or hyphens. The user name can't be
PUBLIC
. -
Must contain only lowercase letters, numbers, underscore, plus sign, period (dot), at symbol (@), or hyphen.
-
The first character must be a letter.
-
Must not contain a colon (:) or a slash (/).
-
Cannot be a reserved word. A list of reserved words can be found in Reserved Words in the Amazon Redshift Database Developer Guide.
Sourcepub fn master_user_password(&self) -> Option<&str>
pub fn master_user_password(&self) -> Option<&str>
The password associated with the admin user account for the cluster that is being created.
You can't use MasterUserPassword
if ManageMasterPassword
is true
.
Constraints:
-
Must be between 8 and 64 characters in length.
-
Must contain at least one uppercase letter.
-
Must contain at least one lowercase letter.
-
Must contain one number.
-
Can be any printable ASCII character (ASCII code 33-126) except
'
(single quote),"
(double quote),\
,/
, or@
.
Sourcepub fn cluster_security_groups(&self) -> &[String]
pub fn cluster_security_groups(&self) -> &[String]
A list of security groups to be associated with this cluster.
Default: The default cluster security group for Amazon Redshift.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .cluster_security_groups.is_none()
.
Sourcepub fn vpc_security_group_ids(&self) -> &[String]
pub fn vpc_security_group_ids(&self) -> &[String]
A list of Virtual Private Cloud (VPC) security groups to be associated with the cluster.
Default: The default VPC security group is associated with the 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 cluster_subnet_group_name(&self) -> Option<&str>
pub fn cluster_subnet_group_name(&self) -> Option<&str>
The name of a cluster subnet group to be associated with this cluster.
If this parameter is not provided the resulting cluster will be deployed outside virtual private cloud (VPC).
Sourcepub fn availability_zone(&self) -> Option<&str>
pub fn availability_zone(&self) -> Option<&str>
The EC2 Availability Zone (AZ) in which you want Amazon Redshift to provision the cluster. For example, if you have several EC2 instances running in a specific Availability Zone, then you might want the cluster to be provisioned in the same zone in order to decrease network latency.
Default: A random, system-chosen Availability Zone in the region that is specified by the endpoint.
Example: us-east-2d
Constraint: The specified Availability Zone must be in the same region as the current endpoint.
Sourcepub fn preferred_maintenance_window(&self) -> Option<&str>
pub fn preferred_maintenance_window(&self) -> Option<&str>
The weekly time range (in UTC) during which automated cluster maintenance can occur.
Format: ddd:hh24:mi-ddd:hh24:mi
Default: A 30-minute window selected at random from an 8-hour block of time per region, occurring on a random day of the week. For more information about the time blocks for each region, see Maintenance Windows in Amazon Redshift Cluster Management Guide.
Valid Days: Mon | Tue | Wed | Thu | Fri | Sat | Sun
Constraints: Minimum 30-minute window.
Sourcepub fn cluster_parameter_group_name(&self) -> Option<&str>
pub fn cluster_parameter_group_name(&self) -> Option<&str>
The name of the parameter group to be associated with this cluster.
Default: The default Amazon Redshift cluster parameter group. For information about the default parameter group, go to Working with Amazon Redshift Parameter Groups
Constraints:
-
Must be 1 to 255 alphanumeric characters or hyphens.
-
First character must be a letter.
-
Cannot end with a hyphen or contain two consecutive hyphens.
Sourcepub fn automated_snapshot_retention_period(&self) -> Option<i32>
pub fn automated_snapshot_retention_period(&self) -> Option<i32>
The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with CreateClusterSnapshot
.
You can't disable automated snapshots for RA3 node types. Set the automated retention period from 1-35 days.
Default: 1
Constraints: Must be a value from 0 to 35.
Sourcepub fn manual_snapshot_retention_period(&self) -> Option<i32>
pub fn manual_snapshot_retention_period(&self) -> Option<i32>
The default number of days to retain a manual snapshot. If the value is -1, the snapshot is retained indefinitely. This setting doesn't change the retention period of existing snapshots.
The value must be either -1 or an integer between 1 and 3,653.
Sourcepub fn port(&self) -> Option<i32>
pub fn port(&self) -> Option<i32>
The port number on which the cluster accepts incoming connections.
The cluster is accessible only via the JDBC and ODBC connection strings. Part of the connection string requires the port on which the cluster will listen for incoming connections.
Default: 5439
Valid Values:
-
For clusters with ra3 nodes - Select a port within the ranges
5431-5455
or8191-8215
. (If you have an existing cluster with ra3 nodes, it isn't required that you change the port to these ranges.) -
For clusters with dc2 nodes - Select a port within the range
1150-65535
.
Sourcepub fn cluster_version(&self) -> Option<&str>
pub fn cluster_version(&self) -> Option<&str>
The version of the Amazon Redshift engine software that you want to deploy on the cluster.
The version selected runs on all the nodes in the cluster.
Constraints: Only version 1.0 is currently available.
Example: 1.0
Sourcepub fn allow_version_upgrade(&self) -> Option<bool>
pub fn allow_version_upgrade(&self) -> Option<bool>
If true
, major version upgrades can be applied during the maintenance window to the Amazon Redshift engine that is running on the cluster.
When a new major version of the Amazon Redshift engine is released, you can request that the service automatically apply upgrades during the maintenance window to the Amazon Redshift engine that is running on your cluster.
Default: true
Sourcepub fn number_of_nodes(&self) -> Option<i32>
pub fn number_of_nodes(&self) -> Option<i32>
The number of compute nodes in the cluster. This parameter is required when the ClusterType parameter is specified as multi-node
.
For information about determining how many nodes you need, go to Working with Clusters in the Amazon Redshift Cluster Management Guide.
If you don't specify this parameter, you get a single-node cluster. When requesting a multi-node cluster, you must specify the number of nodes that you want in the cluster.
Default: 1
Constraints: Value must be at least 1 and no more than 100.
Sourcepub fn publicly_accessible(&self) -> Option<bool>
pub fn publicly_accessible(&self) -> Option<bool>
If true
, the cluster can be accessed from a public network.
Default: false
Sourcepub fn encrypted(&self) -> Option<bool>
pub fn encrypted(&self) -> Option<bool>
If true
, the data in the cluster is encrypted at rest. If you set the value on this parameter to false
, the request will fail.
Default: true
Sourcepub fn hsm_client_certificate_identifier(&self) -> Option<&str>
pub fn hsm_client_certificate_identifier(&self) -> Option<&str>
Specifies the name of the HSM client certificate the Amazon Redshift cluster uses to retrieve the data encryption keys stored in an HSM.
Sourcepub fn hsm_configuration_identifier(&self) -> Option<&str>
pub fn hsm_configuration_identifier(&self) -> Option<&str>
Specifies the name of the HSM configuration that contains the information the Amazon Redshift cluster can use to retrieve and store keys in an HSM.
Sourcepub fn elastic_ip(&self) -> Option<&str>
pub fn elastic_ip(&self) -> Option<&str>
The Elastic IP (EIP) address for the cluster.
Constraints: The cluster must be provisioned in EC2-VPC and publicly-accessible through an Internet gateway. Don't specify the Elastic IP address for a publicly accessible cluster with availability zone relocation turned on. For more information about provisioning clusters in EC2-VPC, go to Supported Platforms to Launch Your Cluster in the Amazon Redshift Cluster Management Guide.
A list of tag instances.
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 kms_key_id(&self) -> Option<&str>
pub fn kms_key_id(&self) -> Option<&str>
The Key Management Service (KMS) key ID of the encryption key that you want to use to encrypt data in the cluster.
Sourcepub fn enhanced_vpc_routing(&self) -> Option<bool>
pub fn enhanced_vpc_routing(&self) -> Option<bool>
An option that specifies whether to create the cluster with enhanced VPC routing enabled. To create a cluster that uses enhanced VPC routing, the cluster must be in a VPC. For more information, see Enhanced VPC Routing in the Amazon Redshift Cluster Management Guide.
If this option is true
, enhanced VPC routing is enabled.
Default: false
Sourcepub fn additional_info(&self) -> Option<&str>
pub fn additional_info(&self) -> Option<&str>
Reserved.
Sourcepub fn iam_roles(&self) -> &[String]
pub fn iam_roles(&self) -> &[String]
A list of Identity and Access Management (IAM) roles that can be used by the cluster to access other Amazon Web Services services. You must supply the IAM roles in their Amazon Resource Name (ARN) format.
The maximum number of IAM roles that you can associate is subject to a quota. For more information, go to Quotas and limits in the Amazon Redshift Cluster Management 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 .iam_roles.is_none()
.
Sourcepub fn maintenance_track_name(&self) -> Option<&str>
pub fn maintenance_track_name(&self) -> Option<&str>
An optional parameter for the name of the maintenance track for the cluster. If you don't provide a maintenance track name, the cluster is assigned to the current
track.
Sourcepub fn snapshot_schedule_identifier(&self) -> Option<&str>
pub fn snapshot_schedule_identifier(&self) -> Option<&str>
A unique identifier for the snapshot schedule.
Sourcepub fn availability_zone_relocation(&self) -> Option<bool>
pub fn availability_zone_relocation(&self) -> Option<bool>
The option to enable relocation for an Amazon Redshift cluster between Availability Zones after the cluster is created.
Sourcepub fn aqua_configuration_status(&self) -> Option<&AquaConfigurationStatus>
pub fn aqua_configuration_status(&self) -> Option<&AquaConfigurationStatus>
This parameter is retired. It does not set the AQUA configuration status. Amazon Redshift automatically determines whether to use AQUA (Advanced Query Accelerator).
Sourcepub fn default_iam_role_arn(&self) -> Option<&str>
pub fn default_iam_role_arn(&self) -> Option<&str>
The Amazon Resource Name (ARN) for the IAM role that was set as default for the cluster when the cluster was created.
Sourcepub fn load_sample_data(&self) -> Option<&str>
pub fn load_sample_data(&self) -> Option<&str>
A flag that specifies whether to load sample data once the cluster is created.
Sourcepub fn manage_master_password(&self) -> Option<bool>
pub fn manage_master_password(&self) -> Option<bool>
If true
, Amazon Redshift uses Secrets Manager to manage this cluster's admin credentials. You can't use MasterUserPassword
if ManageMasterPassword
is true. If ManageMasterPassword
is false or not set, Amazon Redshift uses MasterUserPassword
for the admin user account's password.
Sourcepub fn master_password_secret_kms_key_id(&self) -> Option<&str>
pub fn master_password_secret_kms_key_id(&self) -> Option<&str>
The ID of the Key Management Service (KMS) key used to encrypt and store the cluster's admin credentials secret. You can only use this parameter if ManageMasterPassword
is true.
Sourcepub fn ip_address_type(&self) -> Option<&str>
pub fn ip_address_type(&self) -> Option<&str>
The IP address types that the cluster supports. Possible values are ipv4
and dualstack
.
Sourcepub fn multi_az(&self) -> Option<bool>
pub fn multi_az(&self) -> Option<bool>
If true, Amazon Redshift will deploy the cluster in two Availability Zones (AZ).
Sourcepub fn redshift_idc_application_arn(&self) -> Option<&str>
pub fn redshift_idc_application_arn(&self) -> Option<&str>
The Amazon resource name (ARN) of the Amazon Redshift IAM Identity Center application.
Source§impl CreateClusterInput
impl CreateClusterInput
Sourcepub fn builder() -> CreateClusterInputBuilder
pub fn builder() -> CreateClusterInputBuilder
Creates a new builder-style object to manufacture CreateClusterInput
.
Trait Implementations§
Source§impl Clone for CreateClusterInput
impl Clone for CreateClusterInput
Source§fn clone(&self) -> CreateClusterInput
fn clone(&self) -> CreateClusterInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for CreateClusterInput
impl Debug for CreateClusterInput
Source§impl PartialEq for CreateClusterInput
impl PartialEq for CreateClusterInput
impl StructuralPartialEq for CreateClusterInput
Auto Trait Implementations§
impl Freeze for CreateClusterInput
impl RefUnwindSafe for CreateClusterInput
impl Send for CreateClusterInput
impl Sync for CreateClusterInput
impl Unpin for CreateClusterInput
impl UnwindSafe for CreateClusterInput
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);