tests/resource/aws_securityhub_member: Handle BadRequestException in CheckDestroy #16408
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…CheckDestroy Reference: https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_ListMembers.html Previously the test would pass but the CheckDestroy would fail: ``` === RUN TestAccAWSSecurityHub_serial/Member/invite TestAccAWSSecurityHub_serial/Member/invite: testing_new.go:63: Error running post-test destroy, there may be dangling resources: BadRequestException: status code: 400, request id: 34dfc5cd-16bb-4e31-9924-6b060f6f30b7 === RUN TestAccAWSSecurityHub_serial/Member/basic TestAccAWSSecurityHub_serial/Member/basic: testing_new.go:63: Error running post-test destroy, there may be dangling resources: BadRequestException: status code: 400, request id: 5049c5b7-be35-4fd2-93d3-4b58e13c7140 ``` This error code is not listed in the API Reference, but the same exact call is used in the CheckExists function, so seems related to only when SecurityHub has been disabled after the test has been completed. Output from acceptance testing: ``` --- PASS: TestAccAWSSecurityHub_serial (28.16s) --- PASS: TestAccAWSSecurityHub_serial/Member (28.16s) --- PASS: TestAccAWSSecurityHub_serial/Member/invite (14.81s) --- PASS: TestAccAWSSecurityHub_serial/Member/basic (13.35s) ```
bflad
added
tests
|
This has been released in version 3.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 for triage. Thanks! |
|
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! |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Reference: #16404 (will fix the acceptance testing prior to testing this change)
Reference: https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_ListMembers.html
Release note for CHANGELOG:
Previously the test would pass but the CheckDestroy would fail:
This error code is not listed in the API Reference, but the same exact call is used in the CheckExists function, so seems related to only when SecurityHub has been disabled after the test has been completed.
Output from acceptance testing: