Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

terraform test: skip destroy step for empty run blocks #34331

Merged
merged 1 commit into from
Nov 30, 2023

Conversation

liamcervante
Copy link
Member

@liamcervante liamcervante commented Nov 30, 2023

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.

@liamcervante liamcervante added the 1.6-backport If you add this label to a PR before merging, backport-assistant will open a new PR once merged label Nov 30, 2023
@liamcervante liamcervante requested a review from a team November 30, 2023 09:12
@liamcervante liamcervante merged commit 9ea1aa0 into main Nov 30, 2023
6 checks passed
Copy link

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

Copy link

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 contributions.
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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 31, 2023
@liamcervante liamcervante deleted the liamcervante/skip-destroy branch February 23, 2024 13:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
1.6-backport If you add this label to a PR before merging, backport-assistant will open a new PR once merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants