Add dual stack support to Global Accelerator

[bschaatsbergen]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Closes #26023

Output from acceptance testing:

bruno@pop-os ~/G/terraform-provider-aws (f/ipv6-global-accelerator)> make testacc TESTS=TestAccGlobalAcceleratorAccelerator_ PKG=globalaccelerator                                               (base) 
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/globalaccelerator/... -v -count 1 -parallel 20 -run='TestAccGlobalAcceleratorAccelerator_'  -timeout 180m
=== RUN   TestAccGlobalAcceleratorAccelerator_basic
=== PAUSE TestAccGlobalAcceleratorAccelerator_basic
=== RUN   TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack
=== PAUSE TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack
=== RUN   TestAccGlobalAcceleratorAccelerator_disappears
=== PAUSE TestAccGlobalAcceleratorAccelerator_disappears
=== RUN   TestAccGlobalAcceleratorAccelerator_update
=== PAUSE TestAccGlobalAcceleratorAccelerator_update
=== RUN   TestAccGlobalAcceleratorAccelerator_attributes
=== PAUSE TestAccGlobalAcceleratorAccelerator_attributes
=== RUN   TestAccGlobalAcceleratorAccelerator_tags
=== PAUSE TestAccGlobalAcceleratorAccelerator_tags
=== CONT  TestAccGlobalAcceleratorAccelerator_basic
=== CONT  TestAccGlobalAcceleratorAccelerator_update
=== CONT  TestAccGlobalAcceleratorAccelerator_disappears
=== CONT  TestAccGlobalAcceleratorAccelerator_tags
=== CONT  TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack
=== CONT  TestAccGlobalAcceleratorAccelerator_attributes
--- PASS: TestAccGlobalAcceleratorAccelerator_disappears (70.96s)
--- PASS: TestAccGlobalAcceleratorAccelerator_basic (78.94s)
--- PASS: TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack (80.37s)
--- PASS: TestAccGlobalAcceleratorAccelerator_tags (115.19s)
--- PASS: TestAccGlobalAcceleratorAccelerator_update (215.47s)
--- PASS: TestAccGlobalAcceleratorAccelerator_attributes (330.73s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/globalaccelerator  330.789s

[bschaatsbergen]

This PR is pending the aws-sdk-go update to 1.44.64

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccGlobalAcceleratorAccelerator_basic\|TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack' PKG=globalaccelerator ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/globalaccelerator/... -v -count 1 -parallel 2  -run=TestAccGlobalAcceleratorAccelerator_basic\|TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack -timeout 180m
=== RUN   TestAccGlobalAcceleratorAccelerator_basic
=== PAUSE TestAccGlobalAcceleratorAccelerator_basic
=== RUN   TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack
=== PAUSE TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack
=== CONT  TestAccGlobalAcceleratorAccelerator_basic
=== CONT  TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack
--- PASS: TestAccGlobalAcceleratorAccelerator_basic (68.56s)
--- PASS: TestAccGlobalAcceleratorAccelerator_ipAddressType_dualStack (74.97s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/globalaccelerator	78.959s

[ewbankkit]

@bschaatsbergen Thanks for the contribution 🎉 👏.

[github-actions]

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

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[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.