aws_eks_node_group: allow name to be optional

[troyready]

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

Not all node group properties can be updated via the API, making many changes require a replacement of the resource. To make this seamless with create_before_destroy (instead of generating a "already exists with name" error), Terraform should allow for the name to be automatically computed.

Release note for CHANGELOG:

aws_eks_node_group: allow name to be automatically computed

Output from acceptance testing:

$ make testacc TESTARGS='-run=func TestAccAWSEksNodeGroup_basic'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=func TestAccAWSEksNodeGroup_basic -timeout 120m
=== RUN   TestAccAWSIoTTopicRule_step_functions
=== PAUSE TestAccAWSIoTTopicRule_step_functions
=== CONT  TestAccAWSIoTTopicRule_step_functions
--- PASS: TestAccAWSIoTTopicRule_step_functions (35.18s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	35.216s

[mfreebairn-r7]

Are there any mods available to review & approve this? Need this to enable easily updating my cluster instance types without leaving me with 0 compute

[Skaronator]

There are currently 2 PRs fixing the exact same issue we have: This one & #13938

@breathingdust @bflad
Is there any chance to get one of them reviewed & merged? I'm not a golang developer but since the code in both PRs are almost Identical they should be fine. 😘

[ewbankkit]

@troyready Thanks for the contribution 👏.
I am going to close this PR as a duplicate of #13938 solely because the linked PR has an acceptance test.
I will try including your commit so that you will get joint attribution.

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