data_source aws_ses_domain_identity aws_ses_email_identity

[danquack]

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

Relates OR Closes #16878

Output from acceptance testing:

$  make testacc TESTARGS="-run=TestAccSESDomainIdentityDataSource_basic" PKG_NAME="./internal/service/ses" ACCTEST_PARALLELISM=3
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ././internal/service/ses/... -v -count 1 -parallel 3 -run=TestAccSESDomainIdentityDataSource_basic TestAccSESEmailIdentityDataSource_basic TestAccSESEmailIdentityDataSource_trailingPeriod -timeout 180m
=== RUN   TestAccSESDomainIdentityDataSource_basic
=== PAUSE TestAccSESDomainIdentityDataSource_basic
=== CONT  TestAccSESDomainIdentityDataSource_basic
--- PASS: TestAccSESDomainIdentityDataSource_basic (23.53s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/ses	25.080s
$ make testacc TESTARGS="-run=TestAccSESEmailIdentityDataSource_basic" PKG_NAME="./internal/service/ses" ACCTEST_PARALLELISM=3 
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ././internal/service/ses/... -v -count 1 -parallel 3 -run=TestAccSESEmailIdentityDataSource_basic -timeout 180m
=== RUN   TestAccSESEmailIdentityDataSource_basic
=== PAUSE TestAccSESEmailIdentityDataSource_basic
=== CONT  TestAccSESEmailIdentityDataSource_basic
--- PASS: TestAccSESEmailIdentityDataSource_basic (22.20s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/ses	23.743s
$ make testacc TESTARGS="-run=TestAccSESEmailIdentityDataSource_trailingPeriod" PKG_NAME="./internal/service/ses" ACCTEST_PARALLELISM=3   
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ././internal/service/ses/... -v -count 1 -parallel 3 -run=TestAccSESEmailIdentityDataSource_trailingPeriod -timeout 180m
=== RUN   TestAccSESEmailIdentityDataSource_trailingPeriod
=== PAUSE TestAccSESEmailIdentityDataSource_trailingPeriod
=== CONT  TestAccSESEmailIdentityDataSource_trailingPeriod
--- PASS: TestAccSESEmailIdentityDataSource_trailingPeriod (22.08s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/ses	23.651s
...

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccSESDomainIdentityDataSource_\|TestAccSESEmailIdentityDataSource_' PKG=ses
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/ses/... -v -count 1 -parallel 20 -run=TestAccSESDomainIdentityDataSource_\|TestAccSESEmailIdentityDataSource_ -timeout 180m
=== RUN   TestAccSESDomainIdentityDataSource_basic
=== PAUSE TestAccSESDomainIdentityDataSource_basic
=== RUN   TestAccSESEmailIdentityDataSource_basic
=== PAUSE TestAccSESEmailIdentityDataSource_basic
=== RUN   TestAccSESEmailIdentityDataSource_trailingPeriod
=== PAUSE TestAccSESEmailIdentityDataSource_trailingPeriod
=== CONT  TestAccSESDomainIdentityDataSource_basic
=== CONT  TestAccSESEmailIdentityDataSource_basic
=== CONT  TestAccSESEmailIdentityDataSource_trailingPeriod
--- PASS: TestAccSESEmailIdentityDataSource_trailingPeriod (18.94s)
--- PASS: TestAccSESEmailIdentityDataSource_basic (20.00s)
--- PASS: TestAccSESDomainIdentityDataSource_basic (20.17s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/ses	25.099s

[ewbankkit]

@danquack Thanks for the contribution 🎉 👏.

[github-actions]

This functionality has been released in v3.71.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.