fix: TFE remote ops detection for >= tf 1.0.0 #1687
Merged
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
chenrui333
changed the title
msarvar
referenced
this pull request
in lyft/atlantis
Sep 27, 2021
This was referenced Dec 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Atlantis fails during the plan step when using TFE remote ops and Terraform version 1.0.0. (Same issue with 1.0.1). This is due to a slight change in the error message that gets printed when trying to run plan with the -out param on a TFE workspace set up for remote operations. This change fixes that by adding the Terraform 1.0.{0,1} specific error message to the remote ops detection logic.