terraform test: skip destroy step for empty run blocks #34331
Merged
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.
This PR updates the testing framework so that it won't attempt to destroy run blocks that only contain data sources.
This doesn't really fix the underlying issue that was exposed by #34280 and then mostly fixed in #34293, but it does mean that users that are following our tutorials and docs will not encounter that particular issue. Also, we can backport this change in a way we couldn't with the actual fix. This should make users in the 1.6 series have a slightly better time when following our docs and tutorials.
CHANGELOG
BUG FIXES
terraform test
: Stop attempting to destroy run blocks that have no actual infrastructure to destroy. This fixes an issue where attempts to destroy "verification" run blocks that load only data sources would fail if the underlying infrastructure referenced by the run blocks had already been destroyed.