elb_target_group: support ip_address_type

[SipSeb]

Summary

AWS added the support for IPv6 backends recently. Currently, I cannot manage those target groups automatically. When trying, I get an error.

botocore.exceptions.ClientError: An error occurred (ValidationError) when calling the RegisterTargets operation: The IP address 'affe:affe:affe::affe' is not a valid IPv4 address

When querying a manually created target group, I get an ip_address_type property.

            {
                "deregistration_delay_connection_termination_enabled": "false",
                "deregistration_delay_timeout_seconds": "300",
                "health_check_enabled": true,
                "health_check_interval_seconds": 30,
                "health_check_port": "traffic-port",
                "health_check_protocol": "TCP",
                "health_check_timeout_seconds": 10,
                "healthy_threshold_count": 3,
                "ip_address_type": "ipv6",
                "load_balancer_arns": [],
                "port": 80,
                "preserve_client_ip_enabled": "false",
                "protocol": "TCP",
                "proxy_protocol_v2_enabled": "false",
                "stickiness_enabled": "false",
                "stickiness_type": "source_ip",
                "tags": {},
                "target_group_arn": "arn:aws:elasticloadbalancing:eu-central-1:1234567890:targetgroup/tg-v6/715c73821da67a3f",
                "target_group_name": "tg-v6",
                "target_type": "ip",
                "unhealthy_threshold_count": 3,
                "vpc_id": "vpc-foobar"
            }

Issue Type

Feature Idea

Component Name

elb_target_group

Additional Information

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• [plugins/modules/elb_target_group.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/elb_target_group.py)

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @jillr @markuman @s-hertel @tremble
click here for bot help

[alinabuzachis]

@SipSeb Thank you for this feature idea. Would you be willing to open a PR to add support for ip_address_type?