Open Aethylred opened 10 years ago
The way I work around this is to have two module paths configured in puppet, one that has librarian-puppet managed modules and one that doesn't.
or you can put your git modules into ./my_modules and use
mod 'mymodule', :path => "./my_modules/mymodule"
I'm using two local module directories in my Puppetfile as @carlossg suggested. I bumped into the issue that dependencies via :path based modules were not fetched, but I fixed this in #184.
@rodjek or @carlossg can one of you make a new release of librarian-puppet?
What ended up being the cleanest solution? I'm leaning toward a separate profiles repository, pulled in via librarian-puppet with the path option.
until somebody implements a not-so-destructive clean goal, just put them in a different dir and use :path
entries in Puppetfile
mod 'mymodule', :path => "./my_modules/mymodule"
I would suggest using local
like r10k: https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#local
We would use an already given standard and could work with local modules.
I'm trying to implement something similar to the Roles and Profiles setup as described by @hunner (and an example ).
When running:
it wipes the modules directories completely, removing the
role
andprofile
classes (say hooray forgit reset --hard HEAD
).Could there be a flag on a module to make librarian-puppet leave it alone?
Something like:
processing a list might work better: