feat: add support for "single-outpost" outpost_mode and preferred_outpost_arn to elasticache

[weizhangfd]

Description

Add Outpost support to aws_elasticache_cluster.

Relations

Closes #18460

References

Output from Acceptance Testing

$ make testacc TESTS=TestAccElastiCacheCluster_outpostARN_none PKG=elasticache
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/elasticache/... -v -count 1 -parallel 20 -run='TestAccElastiCacheCluster_outpostARN_none'  -timeout 180m
=== RUN   TestAccElastiCacheCluster_outpostARN_none
=== PAUSE TestAccElastiCacheCluster_outpostARN_none
=== CONT  TestAccElastiCacheCluster_outpostARN_none
--- PASS: TestAccElastiCacheCluster_outpostARN_none (2.30s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/elasticache        5.538s

...

Unfortunately I don't have an outpost instance available to run all the acceptance tests in outpost mode, apologies. Could I please trouble you to help me running them? Please feel free to edit the code.

[github-actions]

Community Note

Voting for Prioritization

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

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

Welcome @weizhangfd 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccElastiCacheCluster_Engine_redis\|TestAccElastiCacheCluster_outpost\|TestAccElastiCacheClusterDataSource_Data_basic' PKG=elasticache ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/elasticache/... -v -count 1 -parallel 2  -run=TestAccElastiCacheCluster_Engine_redis\|TestAccElastiCacheCluster_outpost\|TestAccElastiCacheClusterDataSource_Data_basic -timeout 180m
=== RUN   TestAccElastiCacheClusterDataSource_Data_basic
=== PAUSE TestAccElastiCacheClusterDataSource_Data_basic
=== RUN   TestAccElastiCacheCluster_Engine_redis
=== PAUSE TestAccElastiCacheCluster_Engine_redis
=== RUN   TestAccElastiCacheCluster_Engine_redis_v5
=== PAUSE TestAccElastiCacheCluster_Engine_redis_v5
=== RUN   TestAccElastiCacheCluster_outpost_memcached
=== PAUSE TestAccElastiCacheCluster_outpost_memcached
=== RUN   TestAccElastiCacheCluster_outpost_redis
=== PAUSE TestAccElastiCacheCluster_outpost_redis
=== RUN   TestAccElastiCacheCluster_outpostID_memcached
=== PAUSE TestAccElastiCacheCluster_outpostID_memcached
=== RUN   TestAccElastiCacheCluster_outpostID_redis
=== PAUSE TestAccElastiCacheCluster_outpostID_redis
=== CONT  TestAccElastiCacheClusterDataSource_Data_basic
=== CONT  TestAccElastiCacheCluster_outpost_redis
    acctest.go:1368: skipping since no Outposts found
--- SKIP: TestAccElastiCacheCluster_outpost_redis (1.86s)
=== CONT  TestAccElastiCacheCluster_Engine_redis_v5
--- PASS: TestAccElastiCacheClusterDataSource_Data_basic (520.98s)
=== CONT  TestAccElastiCacheCluster_outpost_memcached
    acctest.go:1368: skipping since no Outposts found
--- SKIP: TestAccElastiCacheCluster_outpost_memcached (0.52s)
=== CONT  TestAccElastiCacheCluster_Engine_redis
--- PASS: TestAccElastiCacheCluster_Engine_redis_v5 (558.91s)
=== CONT  TestAccElastiCacheCluster_outpostID_redis
    acctest.go:1368: skipping since no Outposts found
--- SKIP: TestAccElastiCacheCluster_outpostID_redis (0.17s)
=== CONT  TestAccElastiCacheCluster_outpostID_memcached
    acctest.go:1368: skipping since no Outposts found
--- SKIP: TestAccElastiCacheCluster_outpostID_memcached (0.23s)
--- PASS: TestAccElastiCacheCluster_Engine_redis (524.86s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/elasticache	1037.641s

[ewbankkit]

@weizhangfd Thanks for the contribution 🎉 👏.
The HashiCorp maintainers don't currently have access to an Outpost so I have noted in the CHANGELOG that this is best-effort.

[github-actions]

This functionality has been released in v4.41.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.