Closed fatmcgav closed 9 years ago
Also, if I put the metadata line above the modules in Puppetfile, then Librarian-puppet fails with an 'Unable to find module on Forge' error.
Full verbose log is: https://gist.github.com/fatmcgav/aa76c69edc495e84b91a#file-librarian-puppet-metadata-first
You shouldn't put modules in the metadata.json if they are not in the forge. Try removing the ones you want from git
Hmm, doesn't feel like the correct process to me...
Surely the metadata.json file should contain all the dependencies that my module has, no matter where they're coming from?!
That is how it works now. metadata.json is only useful for forge modules, as the puppet module tool will only check there.
Ah, cool, cheers :)
I'm trying to use Librarian-Puppet to handle module dependencies for testing etc, by using a combination of metadata and Git sourced modules...
However when I try and run librarian-puppet, I get:
I've got a module with a defined dependencies section in 'metadata.json'.
I've also defined a Puppetfile, with the following contents:
A verbose run looks like: https://gist.github.com/fatmcgav/aa76c69edc495e84b91a#file-librarian-puppet-verbose And the resultant Puppetfile.lock looks like: https://gist.github.com/fatmcgav/aa76c69edc495e84b91a#file-puppetfile-lock
Any ideas?
Cheers Gavin