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
Init force-copy is not "equivalent to providing a "yes" to all confirmation prompts." #17663
Comments
The obvious workaround is This bug is especially annoying when
|
Is there any update on this? We are getting "Error asking for state migration action: input is disabled" even if -force-copy option. Our command :
|
Any update on this @jbardin |
Hey I am also having this same issue. Any update on this? |
Hi folks, The terraform core team is heads-down on the terraform 0.12 release, which is currently feature-frozen. I see that there is already PR open and we will review it once 0.12 is released. In general, the best way to influence our prioritization is by reacting to the original issue comment with 👍, which we can and do report on during prioritization. |
This is still affecting v0.12 |
@jeffmccollum @Lasering and other folks who have upvoted this: I have tried to reproduce this on 0.12.26 with Terraform Cloud ("remote" backend) and AWS S3, and in my tests when I ran I have put together a scripted issue reproduction in https://github.com/danieldreier/terraform-issue-reproductions/tree/master/17663 to help us collaborate on this. Based on my initial attempts to reproduce it, it looks to me like this was resolved at some point, but given how many people have upvoted this, I would appreciate some help and confirmation. I know it's possible I've scripted this wrong. If you are still seeing this behavior on 0.12.26 or an 0.13.0 beta, please make a PR against that reproduction case to show me how to trigger this behavior. |
I am going to close this issue due to both inactivity and the fact that it appears to be resolved, thanks! If there is still a question, I recommend the the community forum, where there are far more people available to help. If there is a bug or you would like to make a feature request, please open a new issue and fill out the template. |
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. |
The setting
force-copy
interraform init
is not 'equivalent to providing a "yes" to all confirmation prompts.'Terraform Version
Steps to Reproduce
terraform init -force-copy
Expected Behavior
Terraform should copy the state to consul without user interaction.
Actual Behavior
Additional Context
The following alternatives were tried:
terraform init -reconfigure -force-copy
same outcome as without thereconfigure
.terraform init -input=false -reconfigure
andterraform init -input=false -reconfigure -force-copy
with the outcomeError asking for state migration action: input is disabled
.The text was updated successfully, but these errors were encountered: