Add oracle specific parameters to option enabled_cloudwatch_logs_exports in rds cluster resource

[sriprasanna]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform VersionTerraform

v0.11.7

Affected Resource(s)

resource "aws_db_instance"

Terraform Configuration Files

resource "aws_db_instance" "new-oracle-db" {
  engine                                             = "oracle-se"
  ...
  enabled_cloudwatch_logs_exports = ["alert", "audit", "listener", "trace"]
}

Debug Output

https://gist.github.com/sriprasanna/e4b964086fb76bfd1befe04bb6a3a049

Panic Output

Expected Behavior

The following logs should be enabled for CloudWatch exports: alert, audit, listener and trace

Actual Behavior

Right now, the available parameters for enabled_cloudwatch_logs_exports are audit, error, general and slowquery. These parameters apply for MySQL but not necessarily to other Databases. Oracle for instance supports alert, audit, listener and trace, on using these parameters validation error is thrown from this code.

Steps to Reproduce

1. terraform plan

Important Factoids

References

• PR where this feature was introduced Add enabled_cloudwatch_logs_exports to rds cluster resource #4875.

[bflad]

Pull request submitted: #5494

[bflad]

In version 1.32.0 of the AWS provider, releasing later this week, you will be able to declare these additional log types. 👍

[bflad]

This has been released in version 1.32.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[ghost]

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!