Complex module outputs seemingly considered `null` instead of computed during plan

drewmullen1 · January 24, 2022, 1:32am

Ive been latently considering this problem more and I have 2 ideas to try:

the local.service_list compares key entries to != null because I used to use terraform custom objects…
The problem could be due to the fact that I’m passing the local to a submodule as a variable. Variables in TF are treated differently at plan and are not capable of waiting. hence why the error is related to the ARC sub-module var.service_list and not the root module local.service_list where the list is initially calculated. I may try to extract the resources from a sub-module and see if that fixes it…

Topic		Replies	Views
Implicit dependency between modules with for_each Terraform	2	644	November 14, 2022
For_each local cannot be determined until apply Terraform	4	750	April 5, 2023
The "for_each" value depends on resource attributes that cannot be determined until apply when used as a module Terraform	2	1301	May 18, 2022
Outputs from child module which is created by for_each Terraform azure	11	3224	January 22, 2021
Passing module outputs back into module with for_each Terraform	0	409	February 27, 2021