-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_rds_cluster_parameter_group does not generate a unique name when specifying name_prefix #1739
Comments
Commenting out |
0.10.7 confirmed. name_prefix combined with create_before_destroy. |
Confirmed in Here is a little workaround I'm successfully using:
which generates strings like
Not as elegant as using |
…rameterGroupName error on creation with generated names and name_prefix References: * #1739 * #7264 Previous output from acceptance testing: ``` --- FAIL: TestAccAWSDBClusterParameterGroup_generatedName_Parameter (8.30s) testing.go:538: Step 0 error: Error applying: 1 error occurred: * aws_rds_cluster_parameter_group.test: 1 error occurred: * aws_rds_cluster_parameter_group.test: Error modifying DB Cluster Parameter Group: InvalidParameterValue: The parameter DBClusterParameterGroupName must be provided and must not be blank. status code: 400, request id: e2a07ba0-ba60-4d24-a8ee-3d7a86cf1793 --- FAIL: TestAccAWSDBClusterParameterGroup_namePrefix_Parameter (8.43s) testing.go:538: Step 0 error: Error applying: 1 error occurred: * aws_rds_cluster_parameter_group.test: 1 error occurred: * aws_rds_cluster_parameter_group.test: Error modifying DB Cluster Parameter Group: InvalidParameterValue: The parameter DBClusterParameterGroupName must be provided and must not be blank. status code: 400, request id: 895b9f34-c88e-46ec-8006-0ee61096cff1 ``` Output from acceptance testing: ``` --- PASS: TestAccAWSDBClusterParameterGroup_disappears (10.98s) --- PASS: TestAccAWSDBClusterParameterGroup_namePrefix (12.80s) --- PASS: TestAccAWSDBClusterParameterGroup_generatedName (12.99s) --- PASS: TestAccAWSDBClusterParameterGroup_namePrefix_Parameter (13.53s) --- PASS: TestAccAWSDBClusterParameterGroup_generatedName_Parameter (13.60s) --- PASS: TestAccAWSDBClusterParameterGroup_withApplyMethod (14.34s) --- PASS: TestAccAWSDBClusterParameterGroup_importBasic (15.56s) --- PASS: TestAccAWSDBClusterParameterGroup_basic (24.07s) ```
The fix for the |
This has been released in version 1.57.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
https://gist.github.com/majormoses/f373836f0219ae37a0079f3938868ce9
Expected Behavior
Terraform should have computed a unique name (using the prefix) and submitted it with the request.
Actual Behavior
It appears that the plan believes it should compute the value but either does and does not submit it or does not compute it. This results in a 400 because the body did not match the requirements:
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
terraform apply
Important Factoids
None
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here?
Not that I saw
The text was updated successfully, but these errors were encountered: