data-source/data_source_aws_iam_group: Retrieve users that are associated to the group

[Vince-Chenal]

Motivation

It is often handy to have access to the mapping between IAM Groups and IAM Users, especially when you can't directly use the group.

For example, you can't give permissions to a group in a S3 Bucket Policy. You need to explicitly give all the ARNs or UserIDs of the users.

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" comments, they generate extra noise for pull request followers and do not help prioritize the request

Closes #10652

Release note for CHANGELOG:

* data-source/data_source_aws_iam_group: Retrieve users that are associated to the group

Output from acceptance testing:

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

[bflad]

Hi @Vince-Chenal 👋 Thank you for submitting this.

It appears there might have been some disconnect between the newer feature request #10652 and a previously existing one #7076, where the earlier one had a previously opened pull request #7132. In these situations the maintainers prefer to work through pull requests in their submitted order to be fair to the original contributor and since the original pull request is mostly ready to go except for a few minor feedback items, we are going to opt to close this one to prevent further confusion.

Apologies for any confusion and thank you again for your contribution.

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