feat: Support setting allowed IPv6 CIDR blocks

[clemensg]

Description

Add an input allowed_ipv6_cidr_blocks to set ipv6_cidr_blocks in the cidr_ingress security group.

Motivation and Context

In the last release, the network_type input was introduced. As allowed_cidr_blocks is assigned to cidr_blocks and this only accepts IPv4 networks, we need a similar way to set the IPv6 CIDR blocks in the cidr_ingress security group when network_type = "DUAL" is used.

Breaking Changes

None

How Has This Been Tested?

I have tested this change with our in-house terraform codebase.

[clemensg]

I noticed that when I am creating a new cluster, I get this error (Terraform 1.3.0):

| Error: Invalid count argument
│
│   on ../../terraform-aws-rds-aurora/main.tf line 348, in resource "aws_security_group_rule" "cidr_ingress":
│  348:   count = local.create_cluster && var.create_security_group && (length(var.allowed_cidr_blocks) > 0 || length(var.allowed_ipv6_cidr_blocks) > 0) ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many instances will be created. To work around this, use the -target argument to first apply only the resources that the count depends on.

Any ideas?

[github-actions[bot]]

This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days

[github-actions[bot]]

This PR was automatically closed because of stale in 10 days

[clemensg]

Ping?

[github-actions[bot]]

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.