Ask Your Question

librarian-puppet with modules in git

asked 2014-03-05 13:50:01 -0600

alextsr gravatar image

updated 2014-03-05 13:51:07 -0600

So, if you're using librarian-puppet it's recommended to not track your modules in git, but I'm creating a workflow with the opposite. Why would that be a bad idea?

To elaborate, we currently have one git repo with just a few modules, profile, role, and a couple of app specific ones that are still in their infancy. We also use several forge modules. Our repo has three branches mapped to the equivalent puppet environments. So my idea for a workflow is this.

Create this structure:

|- manifests/
|- modules/  # Forge modules
|- site/     # Our internal modules
|- Puppetfile

Put it ... (more)

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2014-04-19 19:19:09 -0600

solarkennedy gravatar image

I personally have done this, and I think it is ok. It kinda comes down to how you want to end up distributing your bundle of modules.

Running librarian on the puppet server side alleviates the need have git track all the files of all the external modules, but eh.

I personally like:

| modules/
| vendor/modules/

And, by setting your module path to prefer one over the other, you can make a strong distinction between those modules that are managed by librarian, and those managed by hand. (like you have too)

It will work. Just be on the lookout for cases where a .git folder might accidentally get imported in, those subtrees can be hard to track down.

But yea, I also like the idea of having a single commit be a self contained bump of the Puppetfile and the vendor module files that changed with it.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2014-03-05 13:50:01 -0600

Seen: 715 times

Last updated: Apr 19 '14