Resource Identity: Generate Resource Identity tests for aws_ce_anomaly_subscription

[gdavison]

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Description

Generate Resource Identity tests for aws_ce_anomaly_subscription. Adds option to generate tests with email address parameter

Output from Acceptance Testing

% make testacc TESTS=TestAccCEAnomalySubscription_Identity_ PKG=ce

--- PASS: TestAccCEAnomalySubscription_Identity_Basic (32.11s)
--- PASS: TestAccCEAnomalySubscription_Identity_ExistingResource (85.51s)

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[jar-b]

LGTM 🚀

[jar-b]

An aside - can we start collecting valid arguments for identity tests in the contributor docs, similar to what we do for tags tests?
https://hashicorp.github.io/terraform-provider-aws/resource-tagging/#controlling-test-generation

[github-actions]

Warning

This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.