terraform init doesn't honour input=false or automation flags for invalid workspace

[dennisroche]

Terraform Version

Terraform v1.0.9

Expected Behavior

terraform init -input=false (or TF_IN_AUTOMATION=1 set) command should fail outright if it doesn't have enough information to proceed

Actual Behavior

terraform init was stuck waiting on input/workspace selection until the CICD build timed out.

Steps to Reproduce

export TF_IN_AUTOMATION=true
export TF_WORKSPACE=DOES_NOT_EXIST
terraform init -input=false

Additional Context

Running terraform using the GitHub action hashicorp/setup-terraform@v1 which has a built-in wrapper.

References

Discussed in #21393 but was closed without resolution as reported against terraform 0.11.x.

That issue went on a tangent about defaulting the selection (a bad idea - #21393 (comment)) and then further on to automatic creation of workspace.

[alisdair]

Thanks for reporting this! I can confirm this behaviour is a bug.

[alisdair]

The fix for this has been merged into the v1.0 branch and will go out with the next patch release. Thanks for reporting!

[github-actions]

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.