-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
resource/aws_rds_cluster_instance: Support Performance Insights #2331
Conversation
Any reviewers for this ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @kwent
Thanks for the work here, the overall modifications look very good! :)
However, the new acceptance test if failing with:
=== RUN TestAccAWSRDSClusterInstance_withInstancePerformanceInsights
--- FAIL: TestAccAWSRDSClusterInstance_withInstancePerformanceInsights (109.20s)
testing.go:503: Step 0 error: Error applying: 1 error(s) occurred:
* aws_rds_cluster_instance.cluster_instances: 1 error(s) occurred:
* aws_rds_cluster_instance.cluster_instances: InvalidParameterCombination: Access denied to Performance Insights
status code: 400, request id: 9417a2ac-c09d-4f9a-9d06-50c336ea6167
Is it because it can only runs on Aurora postgres engines?
(As per the documentation: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PerfInsights.html:
Amazon RDS Performance Insights is currently available only for use with Amazon Aurora (PostgreSQL).)
@Ninir Thanks. Yes probably ! I will fix the test. Should i also check against the engine and notify the user that Performance Insights is only available for |
Hi @Ninir, The PR should be in a much better place now. Let me know ! |
Any follow up on this ? cc @Ninir How can i help ? Regards |
Hi @kwent Just ran your tests, and got:
Can you investigate please? thanks! |
I believe i now fixed it. I followed #2419 recommendation. |
@Ninir Mind relaunching the test ? |
Hi @kwent ! Sure, here is the result:
Are you able to run those tests on your own? Tell me if you need any help on that :) |
engine = "aurora-postgresql" | ||
identifier = "tf-cluster-instance-%d" | ||
cluster_identifier = "${aws_rds_cluster.default.id}" | ||
instance_class = "db.r3.large" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Postgresql works with r4 instances (not r3): https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ColinHebert Thanks ! Fixed.
Postgresql works with r4 instances (not r3): https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html
To follow aws-sdk-go name convention
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi folks,
@kwent : just made a change to tests so that the one that was not passing do now. See the latest commit for that!
$ make testacc TEST=./aws TESTARGS='-run=TestAccAWSRDSClusterInstance_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -run=TestAccAWSRDSClusterInstance_ -timeout 120m
=== RUN TestAccAWSRDSClusterInstance_importBasic
--- PASS: TestAccAWSRDSClusterInstance_importBasic (686.87s)
=== RUN TestAccAWSRDSClusterInstance_basic
--- PASS: TestAccAWSRDSClusterInstance_basic (1383.96s)
=== RUN TestAccAWSRDSClusterInstance_namePrefix
--- PASS: TestAccAWSRDSClusterInstance_namePrefix (642.38s)
=== RUN TestAccAWSRDSClusterInstance_generatedName
--- PASS: TestAccAWSRDSClusterInstance_generatedName (644.96s)
=== RUN TestAccAWSRDSClusterInstance_kmsKey
--- PASS: TestAccAWSRDSClusterInstance_kmsKey (721.82s)
=== RUN TestAccAWSRDSClusterInstance_disappears
--- PASS: TestAccAWSRDSClusterInstance_disappears (660.97s)
=== RUN TestAccAWSRDSClusterInstance_withInstanceEnhancedMonitor
--- PASS: TestAccAWSRDSClusterInstance_withInstanceEnhancedMonitor (705.20s)
=== RUN TestAccAWSRDSClusterInstance_withInstancePerformanceInsights
--- PASS: TestAccAWSRDSClusterInstance_withInstancePerformanceInsights (892.01s)
PASS
ok github.com/terraform-providers/terraform-provider-aws/aws 6338.228s
Thanks for the work and reactivity! :) 🚀
resource/aws_rds_cluster_instance: Support Performance Insights
This has been released in terraform-provider-aws version 1.7.0. 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! |
Support Performance Insights for rds_cluster_instance
Fixes: #2198