You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
liamcervante opened this issue
Sep 11, 2023
· 1 comment
· Fixed by #33867
Assignees
Labels
bugconfirmeda Terraform Core team member has reproduced this issueexplaineda Terraform Core team member has described the root cause of this issue in code
main.tftest.hcl... in progress
run "stacked"... pass
run "defaults"... pass
run "custom_defined_apply_defaults"... fail
╷
│ Error: Invalid value for input variable
│
│ The given value is not suitable for var.input declared at main.tf:2,1-17:
│ attributes "default" and "optional" are required.
╵
main.tftest.hcl... tearing down
main.tftest.hcl... fail
Failure! 2 passed, 1 failed.
Steps to Reproduce
terraform init terraform test
Additional Context
We're missing a call to apply the defaults before we convert the variables here.
I've looked at this again, and I think we're taking the wrong approach. We should have the computed input values from the plan already available - so let's just use that? Will see if possible.
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugconfirmeda Terraform Core team member has reproduced this issueexplaineda Terraform Core team member has described the root cause of this issue in code
Terraform Version
`v1.6.0-beta1`
Terraform Configuration Files
Debug Output
N/A
Expected Behavior
Tests should apply defaults and pass.
Actual Behavior
Steps to Reproduce
terraform init
terraform test
Additional Context
We're missing a call to apply the defaults before we convert the variables here.
I've looked at this again, and I think we're taking the wrong approach. We should have the computed input values from the plan already available - so let's just use that? Will see if possible.
References
First discovered by here.
The text was updated successfully, but these errors were encountered: