Latest release (20.30.0) introduced a null error condition bug

[dhudson1]

Description

After the introduction of 20.30.0, we are now unable to deploy when using the following specification to lock the version
down to a particular major release (but keeping options open for additional minor patches):

  version                                  = "~> 20.0"

• ✋ I have searched the open/closed issues and my issue is not listed.

Versions

• Module version [Required]:

• Terraform version:
  Terraform v1.7.5

• Provider version(s):

Terraform v1.7.5
on linux_amd64
+ provider registry.terraform.io/databricks/databricks v1.52.0
+ provider registry.terraform.io/hashicorp/aws v5.78.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.3.5
+ provider registry.terraform.io/hashicorp/null v3.2.3
+ provider registry.terraform.io/hashicorp/random v3.6.3
+ provider registry.terraform.io/hashicorp/time v0.12.1
+ provider registry.terraform.io/hashicorp/tls v4.0.6

Reproduction Code [Required]

Steps to reproduce the behavior:

I am not using workspaces.

There is no local cache, as this is deployed (and destroyed) as part of a DevOps process on the cloud.

I simply re-ran my DevOps process which resulted in this failure.

Expected behavior

Deploying the EKS module should work assuming no extraneous failures from AWS or misconfiguration from our part.

Actual behavior

The build errors out with the following message:

╷
│ Error: Null condition
│ 
│   on .terraform/modules/eks/main.tf line 486, in locals:
│  486:   resolve_conflicts_on_create_default = var.bootstrap_self_managed_addons ? "OVERWRITE" : "NONE"
│     ├────────────────
│     │ var.bootstrap_self_managed_addons is null
│ 
│ The condition value is null. Conditions must either be true or false.
╵

Terminal Output Screenshot(s)

Additional context

This error appears to occur when the bootstrap_self_managed_addons is not explicitly passed to the module. Was this release tested with the default bootstrap_self_managed_addons provided?

[antonbabenko]

This issue has been resolved in version 20.30.1 🎉

[dhudson1]

Thank you very much for the rapid fix!

[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.