Since v2.4.0, r10k allows data to be directed into a specific :install_path from a git repo in the Puppetfile.
See https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#per-item-install-path If you have a separate repo of your "files", you could load that into a directory in the environment's root directory. By using the control-branch tracking -- see https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#control-repo-branch-tracking -- you could put a branch-per-environment into a "files" oriented git repo. Hope that's another interesting solution, Anderson On Wednesday, December 14, 2016 at 8:20:24 AM UTC-6, Robert wrote: > > Hello List, > > I finally managed to migrate our Puppet Master from the standard, simple > setup to a bit more advanced configuration with r10k and a Bitbucket server. > > I converted all our modules into git repositories (one module per repo), > stored them in Bitbucket and configured r10k to deploy the whole > environment. It works and it's cool! > > Now there is just one question mark left*: > - in some modules, under files, I store some bigger binaries (like > apache-maven.tgz or a jdk-1.8.tar.gz) for which I'd like to use .gitignore > files in order to leave these out of the repository, since they would > consume storage space and are easy to download again so they don't need to > be tracked. How could these files still be included in the files directory > after the r10k run? > > Regards > Rp > > * but I'm sure there will be some more later ;) > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e246be5c-9264-4323-b6f3-144d631c8f2c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
