d/cloudwatch_logs_groups - make log_group_name_prefix optional

[DrFaust92]

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 #25155

Output from acceptance testing:

$ make testacc TESTS=TestAccLogsGroupsDataSource_ PKG=logs

--- PASS: TestAccLogsGroupsDataSource_noPrefix (26.84s)
--- PASS: TestAccLogsGroupsDataSource_basic (27.02s)

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccLogsGroupsDataSource_' PKG=logs ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/logs/... -v -count 1 -parallel 2  -run=TestAccLogsGroupsDataSource_ -timeout 180m
=== RUN   TestAccLogsGroupsDataSource_basic
=== PAUSE TestAccLogsGroupsDataSource_basic
=== RUN   TestAccLogsGroupsDataSource_noPrefix
=== PAUSE TestAccLogsGroupsDataSource_noPrefix
=== CONT  TestAccLogsGroupsDataSource_basic
=== CONT  TestAccLogsGroupsDataSource_noPrefix
--- PASS: TestAccLogsGroupsDataSource_basic (18.06s)
--- PASS: TestAccLogsGroupsDataSource_noPrefix (19.52s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/logs	23.223s

[ewbankkit]

@DrFaust92 Thanks for the contribution 🎉 👏.

[ewbankkit]

% make providerlint
==> Checking source code with providerlint...

[github-actions]

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