Upon destroy of eks component "depends on resource attributes that cannot be determined"

[nitrocode]

Found a bug? Maybe our Slack Community can help.

Describe the Bug

When I destroy the eks component, I see this error

│ Error: Invalid count argument
│
│   on .terraform/modules/iam_roles.account_map/modules/remote-state/remote.tf line 6, in data "terraform_remote_state" "remote":
│    6:   count = local.remote_state_enabled && local.backend_type == "remote" ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many instances will be created. To work around this, use the -target
│ argument to first apply only the resources that the count depends on.
╵
╷
│ Error: Invalid count argument
│
│   on .terraform/modules/iam_roles.account_map/modules/remote-state/s3.tf line 6, in data "terraform_remote_state" "s3":
│    6:   count = local.remote_state_enabled && local.backend_type == "s3" ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many instances will be created. To work around this, use the -target
│ argument to first apply only the resources that the count depends on.

Expected Behavior

Allow destruction

Steps to Reproduce

Steps to reproduce the behavior:

1. atmos terraform destroy eks --stack uw2-dev

Additional Context

terraform-yaml-stack-config/modules/remote-state/remote.tf

Lines 5 to 6 in 18239bd

	data "terraform_remote_state" "remote" {
	count = local.remote_state_enabled && local.backend_type == "remote" ? 1 : 0

terraform-yaml-stack-config/modules/remote-state/s3.tf

Lines 5 to 6 in 18239bd

	data "terraform_remote_state" "s3" {
	count = local.remote_state_enabled && local.backend_type == "s3" ? 1 : 0

terraform-yaml-stack-config/modules/remote-state/variables.tf

Lines 30 to 34 in 18239bd

	variable "bypass" {
	type = bool
	description = "Set to true to skip looking up the remote state and just return the defaults"
	default = false
	}

terraform-yaml-stack-config/modules/remote-state/main.tf

Line 34 in 18239bd

remote_state_enabled = ! var.bypass

terraform-yaml-stack-config/modules/remote-state/main.tf

Line 18 in 18239bd

backend_type = try(coalesce(local.remote_state_backend_type, local.config.backend_type), "")

workarounds

I tried setting bypass = ! var.enabled which resulted in the same above error.

The workaround was to destroy the eks component using enabled=false which got around this error.

[Nuru]

Closing as duplicate of hashicorp/terraform#27849 which was resolved in Terraform 1.0. Note that even using Terraform 1.3, this issue will arise if the last terraform apply was from a broken version.

[Nuru]

Looks like this is also due to a new Terraform bug: hashicorp/terraform#32023

[Nuru]

Closing as "fixed" in #56 because there is not much else we can do until hashicorp/terraform#32023 is fixed.