Skip to content
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

tenv 2.2.0 breaks terraform apply: error asking for approval: EOF #192

Closed
ThibaultNocchi opened this issue Jun 27, 2024 · 5 comments
Closed
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@ThibaultNocchi
Copy link

Describe the bug
In tenv 2.2.0, I can't apply as I can't answer yes to the prompt:

Plan: 0 to add, 1 to change, 0 to destroy.
╷
│ Warning: Resource targeting is in effect
│
│ You are creating a plan with the -target option, which means that the result of this plan may not
│ represent all of the changes requested by the current configuration.
│
│ The -target option is not for routine use, and is provided only for exceptional situations such
│ as recovering from errors or mistakes, or when Terraform specifically suggests to use it as part
│ of an error message.
╵

Do you want to perform these actions in workspace "nonprod"?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: ╷
│ Error: error asking for approval: EOF
│
│
╵

I'm guessing it may be linked to #191.

To Reproduce
Steps to reproduce the behavior:

  1. Ensure tenv is v2.2.0
  2. Run a manual TF apply
  3. Get the error message, which stops the apply procedure

Expected behavior
EOF shouldn't be fed to the terraform binary I guess?

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • OS: ArchLinux
  • tofuenv version: 2.2.0
  • terraform: 1.8.4-5 (I haven't tested others)

Additional context
I rollbacked to 2.1.8 and it works.

@kvendingoldo kvendingoldo added the bug Something isn't working label Jun 27, 2024
@kvendingoldo
Copy link
Collaborator

Thank you for reporting, we'll check it asap

@dvaumoron dvaumoron self-assigned this Jun 27, 2024
dvaumoron added a commit that referenced this issue Jun 27, 2024
Signed-off-by: Denis Vaumoron <dvaumoron@gmail.com>
dvaumoron added a commit that referenced this issue Jun 27, 2024
…n error (#193)

* light proxy did not pipe input #191 #192
* fix detect empty display with no compatible

Signed-off-by: Denis Vaumoron <dvaumoron@gmail.com>
@dvaumoron
Copy link
Contributor

@ThibaultNocchi, can you check that things work as expected with v2.2.1 ?

@voron
Copy link

voron commented Jun 27, 2024

2.2.1 fixed it for me

@dvaumoron dvaumoron added the duplicate This issue or pull request already exists label Jun 27, 2024
@dvaumoron
Copy link
Contributor

2.2.1 fixed it for me

Happy to see that, I apologize for this impactful mistake

@dvaumoron dvaumoron closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2024
@ThibaultNocchi
Copy link
Author

It also works for me, thank you for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants