From f255e31c2ce564ae829a7f5a8caaec3887bbc0d1 Mon Sep 17 00:00:00 2001 From: AWS SDK for Go v2 automation user Date: Wed, 5 Feb 2025 19:05:26 +0000 Subject: [PATCH] Update API model --- codegen/sdk-codegen/aws-models/rds.json | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/codegen/sdk-codegen/aws-models/rds.json b/codegen/sdk-codegen/aws-models/rds.json index e147a7292aa..fbc0bb4eddf 100644 --- a/codegen/sdk-codegen/aws-models/rds.json +++ b/codegen/sdk-codegen/aws-models/rds.json @@ -5782,7 +5782,7 @@ } ], "traits": { - "smithy.api#documentation": "

Creates a new DB parameter group.

\n

A DB parameter group is initially created with the default parameters for the\n database engine used by the DB instance. To provide custom values for any of the\n parameters, you must modify the group after creating it using\n ModifyDBParameterGroup. Once you've created a DB parameter group, you need to\n associate it with your DB instance using ModifyDBInstance. When you associate\n a new DB parameter group with a running DB instance, you need to reboot the DB\n instance without failover for the new DB parameter group and associated settings to take effect.

\n

This command doesn't apply to RDS Custom.

\n \n

After you create a DB parameter group, you should wait at least 5 minutes\n before creating your first DB instance that uses that DB parameter group as the default parameter \n group. This allows Amazon RDS to fully complete the create action before the parameter \n group is used as the default for a new DB instance. This is especially important for parameters \n that are critical when creating the default database for a DB instance, such as the character set \n for the default database defined by the character_set_database parameter. You can use the \n Parameter Groups option of the Amazon RDS console or the \n DescribeDBParameters command to verify \n that your DB parameter group has been created or modified.

\n ", + "smithy.api#documentation": "

Creates a new DB parameter group.

\n

A DB parameter group is initially created with the default parameters for the\n database engine used by the DB instance. To provide custom values for any of the\n parameters, you must modify the group after creating it using\n ModifyDBParameterGroup. Once you've created a DB parameter group, you need to\n associate it with your DB instance using ModifyDBInstance. When you associate\n a new DB parameter group with a running DB instance, you need to reboot the DB\n instance without failover for the new DB parameter group and associated settings to take effect.

\n

This command doesn't apply to RDS Custom.

", "smithy.api#examples": [ { "title": "To create a DB parameter group", @@ -6802,7 +6802,7 @@ "DataFilter": { "target": "com.amazonaws.rds#DataFilter", "traits": { - "smithy.api#documentation": "

Data filtering options for the integration. For more information, see \n Data filtering for Aurora zero-ETL integrations with Amazon Redshift.\n

\n

Valid for: Integrations with Aurora MySQL source DB clusters only

" + "smithy.api#documentation": "

Data filtering options for the integration. For more information, see \n Data filtering for Aurora zero-ETL integrations with Amazon Redshift\n or\n Data filtering for Amazon RDS zero-ETL integrations with Amazon Redshift.\n

" } }, "Description": { @@ -7156,7 +7156,7 @@ "AllocatedStorage": { "target": "com.amazonaws.rds#IntegerOptional", "traits": { - "smithy.api#documentation": "

For all database engines except Amazon Aurora, AllocatedStorage specifies the allocated storage size in gibibytes (GiB). \n For Aurora, AllocatedStorage always returns 1, because Aurora DB cluster storage size isn't fixed, but instead automatically\n adjusts as needed.

" + "smithy.api#documentation": "

\n AllocatedStorage specifies the allocated storage size in gibibytes (GiB). \n For Aurora, AllocatedStorage can vary because Aurora DB cluster storage size adjusts as needed.

" } }, "AvailabilityZones": { @@ -12311,7 +12311,7 @@ "DeleteAutomatedBackups": { "target": "com.amazonaws.rds#BooleanOptional", "traits": { - "smithy.api#documentation": "

Specifies whether to remove automated backups immediately after the DB\n cluster is deleted. This parameter isn't case-sensitive. The default is to remove \n automated backups immediately after the DB cluster is deleted.

" + "smithy.api#documentation": "

Specifies whether to remove automated backups immediately after the DB\n cluster is deleted. This parameter isn't case-sensitive. The default is to remove \n automated backups immediately after the DB cluster is deleted, unless the Amazon Web Services Backup \n policy specifies a point-in-time restore rule.

" } } }, @@ -22944,7 +22944,7 @@ "NewName": { "target": "com.amazonaws.rds#String", "traits": { - "smithy.api#documentation": "

The new name for the modified DBProxyTarget. An identifier must begin with a letter and must contain only ASCII letters, digits, and hyphens; it can't end with a hyphen or contain two consecutive hyphens.

" + "smithy.api#documentation": "

The new name for the modified DBProxyTarget. An identifier must begin with a letter and must contain only ASCII letters, digits, and hyphens; it can't end with a hyphen or contain two consecutive hyphens.

\n

You can't rename the default target group.

" } } }, @@ -23641,7 +23641,7 @@ } ], "traits": { - "smithy.api#documentation": "

Modifies a zero-ETL integration with Amazon Redshift.

\n \n

Currently, you can only modify integrations that have Aurora MySQL source DB clusters. Integrations with Aurora PostgreSQL and RDS sources currently don't support modifying the integration.

\n ", + "smithy.api#documentation": "

Modifies a zero-ETL integration with Amazon Redshift.

", "smithy.api#examples": [ { "title": "To modify a zero-ETL integration", @@ -23685,7 +23685,7 @@ "DataFilter": { "target": "com.amazonaws.rds#DataFilter", "traits": { - "smithy.api#documentation": "

A new data filter for the integration. For more information, see \n Data filtering for Aurora zero-ETL integrations with Amazon Redshift.

" + "smithy.api#documentation": "

A new data filter for the integration. For more information, see Data filtering\n for Aurora zero-ETL integrations with Amazon Redshift or Data\n filtering for Amazon RDS zero-ETL integrations with Amazon Redshift.

" } }, "Description": {