r10k requires version specification for Forge modules in Puppetfile

[antaflos]

As far as I understand the Puppetfile format allows specifying Forge modules without a version number. It seems r10k doesn't support that:

[R10K::Action::Environment::Deploy - INFO] Deploying environment testing

Runtime error: #<RuntimeError: Module puppetlabs/apt with args [] doesn't have an implementation. (Are you using the right arguments?)>

The Puppetfile in question:

forge "http://forge.puppetlabs.com"

mod "puppetlabs/apt"
...

Adding a version specification makes it work again:

forge "http://forge.puppetlabs.com"

mod "puppetlabs/apt", "1.1.0"

[adrienthebo]

Strange... I could have sworn that I fixed this at some point but it looks like I didn't. Given something like `mod "foo/bar", would you say that the slash is enough to indicate that it's a Forge module? What should the default behavior if a module doesn't have any arguments?

[antaflos]

I think the behaviour should be similar to librarian-puppet, shouldn't it? We haven't used librarian-puppet extensively but I believe the slash is enough to indicate a Forge module and without any version arguments it gets the latest available version.

[adrienthebo]

I agree with you, and I'll update the detection to behave accordingly.

[adrienthebo]

Merged in 9ef872c; this should be released in 1.0.0. Thanks again for the report!

[adrienthebo]

Released in 1.0.0rc1