Glad we cleared up our terminology! I agree that “root module” risks ambiguity, just like you point out. I just realized I never responded to the very last poi

Glad we cleared up our terminology! I agree that “root module” risks ambiguity, just like you point out. I just realized I never responded to the very last point in your original comment. I don’t have, and I don’t think Terraform has, a complete solution to dependencies between root modules. Fortunately, data sources will at least fail if they don’t find what they’re looking for. For me, these failures never come up in production since I’m never using `terraform destroy` there. It does come up in pre-production testing and that’s an area that seems rich with patterns and products on top of Terraform that are controlling order and dependence between root modules. PS thanks for your work on Terraform and Kubernetes.