add support for ca_cert_identifier option

[koneru9999]

Description

This PR adds the option to set the ca_cert_identifier
As the current CA is expiring 5th March 2020 i need to update my clusters to use the new CA before that. The default is currently set to the old one to not break any existing installations.

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL-certificate-rotation.html

Terraform has recently added support for this. hashicorp/terraform-provider-aws#10490

[antonbabenko]

v1.20.0 has been just released.

Thank you @koneru9999 !

[jjuarez]

is this integrated for the Terraform 0.11 branch too?

[antonbabenko]

Yes, Terraform 0.11 users should use v1.20.0 of this module.

[jjuarez]

It seems like not working our case we're facing the error:

Error: module.pre-aurora-01.aws_rds_cluster.this: : invalid or unknown key: ca_cert_identifier

using the v1.20.0 for the terraform 0.11, this makes no sense, new variable with default...
terraform 0.11.14
Providers:

• "null" (1.0.0)...
• "aws" (2.40.0)...
• "random" (2.2.1)...

[antonbabenko]

v1.21.0 has been just released where this is fixed.

I used to believe that people opening pull-requests verify the changes, I was wrong.

RDS Aurora simply does not support ca_cert_identifier option.

Big thanks @jjuarez for your feedback!

[koneru9999]

@antonbabenko My apologies for the PR and wasting your valuable time. I could have checked it more properly. 😞

[antonbabenko]

@koneru9999 That's ok, it happens sometimes. For me, it means that the simplest automatic checks would catch this error. I probably need to prioritize those a bit more. :)

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.