tests/provider: Ensure CheckDestroy functions continue rather than return nil #15847
Labels
linter
Pertains to changes to or issues with the various linters.
stale
Old or inactive issues managed by automation, if no further action taken these will get closed.
technical-debt
Addresses areas of the codebase that need refactoring or redesign.
tests
PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Community Note
Description
CheckDestroy
functions contain afor
loop to check all resource states. If a resource matches and is not found (good in this case), the logic shouldcontinue
the loop instead of immediatelyreturn nil
, otherwise if multiple resources exist they will not all be checked.Potential semgrep Implementation
Example report (where line 481 should be updated):
The text was updated successfully, but these errors were encountered: