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

v0.12: panic: ConfigValueFromHCL2Block used with unknown value #19506

Closed
jtopjian opened this issue Nov 29, 2018 · 1 comment · Fixed by #19521
Closed

v0.12: panic: ConfigValueFromHCL2Block used with unknown value #19506

jtopjian opened this issue Nov 29, 2018 · 1 comment · Fixed by #19521
Labels
Milestone

Comments

@jtopjian
Copy link
Contributor

Hello,

Per a quick chat with @apparentlymart in Slack earlier today, a Terraform OpenStack Provider user reported the following issue:

https://github.com/terraform-providers/terraform-provider-openstack/issues/493 (crash report included)

and patch: https://github.com/terraform-providers/terraform-provider-openstack/pull/494

The issue is being caused by schema.EnvDefaultFunc using default values of "" for TypeBool. Understandably, this doesn't make sense, but it's a historical setting and hasn't been changed since no one has ever reported an issue.

The PR I linked to suggests setting the default values to false. I've also confirmed that setting the default values to nil resolves the problem, too.

The user did their testing with v0.12.0-alpha2 and I can confirm this still exists as of the most recent commit to master.

I'm totally fine with changing the default values of the TypeBool arguments, but wanted to open this issue to:

  1. Report it
  2. See if fixing this in core is more appropriate than making the fix in the provider

Please let me know if you have any other questions or need any other information!

@ghost
Copy link

ghost commented Mar 30, 2020

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.

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants