Return error for non-existent resources when using terraformless export#560
Merged
magodo merged 2 commits intoAzure:mainfrom Sep 4, 2024
Merged
Return error for non-existent resources when using terraformless export#560magodo merged 2 commits intoAzure:mainfrom
magodo merged 2 commits intoAzure:mainfrom
Conversation
ziyeqf
approved these changes
Sep 4, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously, when using terraformless export (i.e.
-tfclient-plugin-path), if the resource/resource group to be exported doesn't exit, an empty HCL block will still be generated.This PR adds additional check after the ReadResource RPC call, to raise error if the state read is nil. This logic exists in
terraform(@internal/terraform/node_resource_import.go), that's why terraform export will correctly raise the error for non-existent resources.