### Terraform Version ```shell Terraform v1.10.0 on linux_amd64 ``` ### Terraform Configuration Files Variable type A ```terraform variable "lambda" { description = "Values for Lambda" type = object({ function_name = string description = string directory = string filename = string handler = string runtime = string timeout = optional(number, 15) }) } variable "external_source_permissions" { description = "Values for external source permissions" type = list(object({ statement_id = string action = optional(string, "lambda:InvokeFunction") principal = string source_arn = string })) default = [] } ``` Variable type B ```terraform variable "lambda" { description = "Values for Lambda" type = object({ function_name = string description = string directory = string filename = string handler = string runtime = string timeout = optional(number, 15) external_source_permissions = optional(list(object({ statement_id = string action = optional(string, "lambda:InvokeFunction") principal = string source_arn = string })), []) }) } ``` ### Debug Output N/A ### Expected Behavior Two modules can depend on one another. Two resources cannot. The above config shows two types of variables - one with a separate ```external_source_permissions``` variable, and one with a single variables that includes ```external_source_permissions``` inside that single variable. Variable type A works fine. Variable type B causes a cyclic dependency in certain situations when there is a cross dependency between two modules. In effect - the difference in how I layout the variables can cause a cyclic dependecy to happen. Is this expected - I appreciate the above config is not enough to determine the issue. The question is whether the way modules are set is expected to potentially cause cyclic issues. If not, then I can send more config to show what exactly happens. ### Actual Behavior N/A ### Steps to Reproduce N/A ### Additional Context _No response_ ### References _No response_ ### Generative AI / LLM assisted development? _No response_