[PUP-6237] PMT should gracefully fall back to older, compatible versions of modules Created: 2016/04/26  Updated: 2020/03/04  Resolved: 2020/03/04

Status: Closed
Project: Puppet
Component/s: PMT
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Normal
Reporter: Eric Sorenson Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: PMT Improvements
Team: Puppet Developer Experience


I coulda sworn there was a ticket to this effect but I've been searching for 20 mins to no avail, so I'll just file a new one.

Currently when you want to puppet module install a module which expresses compatibility with a newer Puppet version than yours, you get an error and a hard failure. Instead, the module should select the latest version of the module which is compatible with your version of Puppet and install that.

This would make it much easier for module authors to maintain independent major-versions of their modules to match capabilities available in different versions of Puppet, while providing a nice user experience.

Comment by Lindsey Smith [ 2017/11/27 ]

Good requirement for future module dependency resolution solution

Comment by Josh Cooper [ 2020/03/04 ]

This makes sense, but hasn't been worked on in many years and is unlikely to be worked on anytime soon. Please reopen if this is still a concern.

Generated at Tue Jul 14 02:29:45 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.