Skip to main content

Registry module usage in stacks

Feature RequestsTerraform registry

To check whether a module/version is being used in a stack, it would be great to have a view in the module page similar to the Resources tab in a stack. This would help us identify is a stack is out of date or which versions of a module we could archive off.

Workaround
Problem
Status: ❌ Rejected3 comments

Log in to comment and vote

Comments3

  • Black Breeze

    •

    May 10, 2025

    Thanks for the suggestion! Just to clarify—Spacelift already tracks usage of modules published in our module registry. Are you referring to modules outside of that? If so, what’s the goal: visibility, standardization, migration help? Would recursive tracking (e.g., modules imported by other modules) be important here? Any more context on what you’re trying to accomplish would help us understand the job to be done.

    • Gold ZeroG

      •

      Oct 28, 2025

      Yes, this is for modules not in spacelift registry (such as github).

    • Silver Pretzel

      •

      Oct 28, 2025

      we have the same requirement, can’t use module registry b/c it’s missing features (like ref can’t be a branch, git-sha, forces you to manage version in a config file, never got it to work with tags).

      We use modules to deploy platforms, so if I’m the database platform team, my platform consumers are users of database terraform module, there is value in that team:

      1. being able to see who their consumers are, what version they are consuming, what variables they are setting
      2. being able to get modules/repos that are using the module via api to perform version up PR creation workflows (it’s probably possible to construct this via graphql today)