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 0.9.1 can't apply plan from a file with S3 backend #12871
Comments
Yeah I am seeing this too after the upgrade. |
I found the issue. The migration code doesn't clear the remote section remotely (it clears it locally in what is called the "data" state which only has the backend configuration). I will fix this early in the AM tomorrow. |
Same thing happens with an Atlas backend, version 0.9.1 |
Yes this is a generic problem with any legacy remote state. Plan on working on a fix here shortly. |
Fixes #12871 We were forgetting to remove the legacy remote state from the actual state value when migrating. This only causes an issue when saving a plan since the plan contains the state itself and causes an error where both a backend + legacy state exist. If saved plans aren't used this causes no noticable issue. Due to buggy upgrades already existing in the wild, I also added code to clear the remote section if it exists in a standard unchanged backend
Fix in attached PR, will be part of 0.9.2. |
Fixes #12871 We were forgetting to remove the legacy remote state from the actual state value when migrating. This only causes an issue when saving a plan since the plan contains the state itself and causes an error where both a backend + legacy state exist. If saved plans aren't used this causes no noticable issue. Due to buggy upgrades already existing in the wild, I also added code to clear the remote section if it exists in a standard unchanged backend
Fixes #12871 We were forgetting to remove the legacy remote state from the actual state value when migrating. This only causes an issue when saving a plan since the plan contains the state itself and causes an error where both a backend + legacy state exist. If saved plans aren't used this causes no noticable issue. Due to buggy upgrades already existing in the wild, I also added code to clear the remote section if it exists in a standard unchanged backend
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
It appears that Terraform is generating invalid plan files when
-out=
is used.Terraform Version
0.9.1
Affected Resource(s)
Core Terraform.
Expected Behavior
Expected to see
terraform apply file.out
apply any pending changes generated byterraform plan -out=file.out
Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
rm file.out
(just in case it exists currently)terraform plan -out=file.out
terraform plan file.out
Current Mitigation
I'm applying changes using
-target=
statements.The text was updated successfully, but these errors were encountered: