-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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 remote state push -force fails lineage check for S3 backend #25761
Comments
For those who come across this issue. I worked around it by using
|
@ConnorGraham Not all backends support the This feature was added for the Terraform Cloud remote backend in this PR: https://github.com/hashicorp/terraform/pull/24696/files. I'm going to mark this as an enhancement for those who maintain the S3 backend, or should you be interested in implementing this feature for the S3 backend. |
An update here: I believe I made a mistake associating this with the remote backend work, and that this is a bug and should be classified as such. I am updating the issue accordingly, also adding the v0.13 label as this was reported on 0.13 as well. I was able to replicate the issue you described with the configuration provided. |
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. |
Terraform Version
v0.12.29
Expected Behavior
The state should be pushed to the remote and forced over any existing state
Actual Behavior
Steps to reproduce
I am using an s3 backend
References
#5663
#15674
#24916
The text was updated successfully, but these errors were encountered: