Gamelift Game Session Queue

[Hinidu]

Replacement for #5397
Original issue #2546

Changes proposed in this pull request:

• New resource aws_gamelift_session_queue

Output from acceptance testing:

$ make testacc TEST=./aws TESTARGS='-run=TestAccAWSGameliftGameSessionQueue_basic'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -parallel 20 -run=TestAccAWSGameliftGameSessionQueue_basic -timeout 120m
=== RUN   TestAccAWSGameliftGameSessionQueue_basic
--- PASS: TestAccAWSGameliftGameSessionQueue_basic (38.62s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	38.630s

The only think I didn't changed is playerLatencyPolicies:

Can there be multiple of these configurations? If not, we should set MaxItems: 1 for this attribute +1

Because there can be many policies.

[Hinidu]

@bflad I think I did everything you asked for and this PR is ready for another review.

[Hinidu]

I've started to implement a resource for matchmaking configurations but to properly test it I need a game session queue because game session queue ARN is one of the required parameters.

[bflad]

Hi again @Hinidu 👋 Thanks so much for the updates! This is pretty close. We should be able to get this in after these minor changes (up to you if you want to implement import or not, but we should change the ID before releasing the initial resource).

[Hinidu]

Hello @bflad! I've replaced ARN by Name as ID and added the import.

[bflad]

Great work, @Hinidu! LGTM 🚀

--- PASS: TestAccAWSGameliftGameSessionQueue_basic (21.46s)

[Hinidu]

Nice! Thank you @bflad for your feedback and merge! Hopefully I will try to implement other GameLift resources soon.

[bflad]

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

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!