Intelligent version conflict resolution for modules without version pinned

[alex-kattathra-johnson]

Terraform Version

v1.12.2

Use Cases

I have provider constraint set on the root and then I've added a bunch of modules without any version constraint. terraform init fails because the version of the module that is selected conflicts with the provider version.

Attempted Solutions

Pinning the versions is the best solution, but it can be not very easy to find the versions with the correct provider versions. And can be tedious when you've got a lot of modules being used.

Proposal

Use a go dep like dependency resolution to resolve conflicting version constraints in an intelligent way.

References

No response

[DasoTD]

I’m also encountering this in large multi-module projects. Manually pinning versions is brittle and hard to maintain at scale. Would love to see an optional “smart resolution” feature similar to how Go/Cargo handle version conflicts. Happy to help sketch out a design or contribute a prototype.