Open gbarton opened 9 years ago
It's probably because you have a dependency in your metadata.json in the ntp module which is missing in your modulepath and librarian puppet tries to resolve the dependency from forge.
Thank you for the reply. Within the Puppetfile I removed the metadata.json and the modulefile, I am just defining within the Puppetfile itself. Here is my current test config:
mod 'ntp', :git => 'git@bla.bla.bla:puppet-modules/ntp.git'
On Sep 25, 2015 7:58 AM, "Fredrik Lindgren" notifications@github.com wrote:
It's probably because you have an dependency in your metadata.json for the ntp module and librarian-puppet tries to download it from forge.
— Reply to this email directly or view it on GitHub https://github.com/rodjek/librarian-puppet/issues/325#issuecomment-143195717 .
Check inside your ntp module for a metadata.json file and if there's a dependency for another module there.
Hi there. I would also like this feature.
I would like to be able to use a Forge in some cases, but disable forge dependency resolution in other cases.
I took a look at the code, but didn't see a straightforward method for making this happen. Pointers would be appreciated.
I'm attempting to use librarian-puppet in an environment that cannot reach puppet forge. (I have no need of an internal forge.)
What I would like to do is just have librarian-puppet interact with git and not forge at all. Is this doable via config currently? It looks like LP is blowing up trying to resolve the module when I do an install, even though I have specified the module as a git one:
mod 'ntp', :git => "git://bla.bla.bla//puppet/ntp.git"