README.md in librarian-puppet-1.4.1 vs README.md in librarian-puppet-1.5.0
- old
+ new
@@ -11,10 +11,11 @@
* Librarian-puppet can reuse the dependencies listed in your `Modulefile` or `metadata.json`
* Forge modules can be installed from [Puppetlabs Forge](https://forge.puppetlabs.com/) or an internal Forge such as [Pulp](http://www.pulpproject.org/)
* Git modules can be installed from a branch, tag or specific commit, optionally using a path inside the repository
* Modules can be installed from GitHub using tarballs, without needing Git installed
+* Modules can be installed from a filesystem path
* Module dependencies are resolved transitively without needing to list all the modules explicitly
Librarian-puppet manages your `modules/` directory for you based on your
`Puppetfile`. Your `Puppetfile` becomes the authoritative source for what
@@ -67,11 +68,15 @@
:git => "git://github.com/puppetlabs/puppetlabs-stdlib.git"
mod 'puppetlabs-apache', '0.6.0',
:github_tarball => 'puppetlabs/puppetlabs-apache'
+ mod 'acme-mymodule', :path => './some_folder'
+ exclusion 'acme-bad_module'
+
+
### Recursive module dependency resolution
When fetching a module all dependencies specified in its
`Modulefile`, `metadata.json` and `Puppetfile` will be resolved and installed.
@@ -131,9 +136,24 @@
:git => "git://github.com/fake/puppet-modules.git",
:path => "modules/apt"
Our puppet infrastructure repository depends on the `apt` module, which we have
stored as a directory under our `puppet-modules` git repos.
+
+ mod 'puppetlabs-apache', '0.6.0',
+ :github_tarball => 'puppetlabs/puppetlabs-apache'
+
+Our puppet infrastructure repository depends on the `puppetlabs-apache` module,
+to be downloaded from GitHub tarball.
+
+ mod 'acme-mymodule', :path => './some_folder'
+
+Our puppet infrastructure repository depends on the `acme-mymodule` module,
+which is already in the filesystem.
+
+ exclusion 'acme-bad_module'
+
+Exclude the module `acme-bad_module` from resolution and installation.
## How to Use
Install librarian-puppet: