Stack module dependency issues

[samkahchiin]

Error when setting cloudwatch_dashboard_view = "detailed"

│ Error: Invalid count argument
│ 
│   on .terraform/modules/stack/cloudwatch/alarm.tf line 226, in resource "aws_cloudwatch_metric_alarm" "error_rate":
│  226:   count               = length(var.alb_arn_suffixes)
│ 
│ 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/stack/cloudwatch/alarm.tf line 379, in resource "aws_cloudwatch_metric_alarm" "extreme_slow_request":
│  379:   count               = length(var.alb_arn_suffixes)
│ 
│ 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.
╵

Common error even setting public_ips to empty array

│ Error: Invalid for_each argument
│ 
│   on .terraform/modules/stack/nat/nat.tf line 44, in resource "aws_route_table_association" "main":
│   44:   for_each  = { for idx, subnet in var.subnet_private_ids : subnet => idx }
│     ├────────────────
│     │ var.subnet_private_ids is tuple with 3 elements
│ 
│ The "for_each" map includes keys derived from resource attributes that cannot be determined until apply, and so Terraform cannot determine the full set of keys that will identify the instances of this resource.
│ 
│ When working with unknown values in for_each, it's better to define the map keys statically in your configuration and place apply-time results only in the map values.
│ 
│ Alternatively, you could use the -target planning option to first apply only the resources that the for_each value depends on, and then apply a second time to fully converge.
╵

In stack/setup

│ Error: Invalid count argument
│ 
│   on .terraform/modules/stack-setup/secrets/secrets.tf line 6, in module "kms-key":
│    6:   count = var.kms_key_id == null ? 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.