Visualising stack–module relationships
During migrations,working on spacelift or terraform setup,
having a clear view of where modules are used across stacks would be incredibly valuable. Extending the Spaces diagram to show this would help teams reason about structure and refactor with confidence.
Log in to comment and vote
Comments3
Natalia Gazda
Jul 16
Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.
Moccasin Wind
Aug 29, 2025
Hi @Natalia Gazda , sorry, somehow I dindt receive a notification for this :)
In recent months, we had to complete two major migrations:
From a forked version of Terraform to OpenTofu
From Terragrunt to plain OpenTofu
We manage around 250 stacks and 80 Terraform modules, and each migration required updates to both stacks and modules. To minimize the impact of "work in progress" changes, we always tried to identify the relationships between modules and the stacks that use them.
Whenever we updated a module and Renovate proposed a version bump, we needed to understand the downstream impact. To do this, we relied on custom scripts that scan our GitHub repositories to map which modules are used in which stacks.
One specific issue we encountered:
After migrating from TG to OpenTofu, a default value in one module changed. Previously, this value was implicitly set by Terragrunt. As a result, we had to identify all affected stacks and either update the values manually or notify the respective owners. The problem wasn’t visible during planning, as the error originated from the provider, which would have led to confusing apply-issues.
It would be extremely helpful to have a centralized overview of module-to-stack (and vice versa) relationships. This would allow us to:
Better assess the impact of changes to shared modules
Identify which stacks would be affected
Coordinate changes with the appropriate owners more effectively
Natalia Gazda
Jul 24, 2025
Hey @Kabiolskij, Nikolai Thanks for this request. I’d love to understand more about the job you’re trying to do.
Could you tell us what specific problems you run into when trying to understand where modules are used? For example—is this mostly during refactors, onboarding, incident response? And how are you working around it today?
It sounds like the goal is to help teams reason about structure more confidently. I’m curious:
what would success look like for you here? What decision or workflow would this unlock—or just make faster and safer?
Appreciate any color you can add! The clearer the job, the better we can shape a solution that actually helps.