This message was deleted.
# puppet
s
This message was deleted.
b
any reason why you dont add modules and site modules to the Puppetfile in the controlrepo?
a
You mean merge the repositories to one mono repo or also include Puppetfile which includes site modules and modules into each environment? Had thought about it as well. It would for sure make coordination easier. Generally when we test stuff we add Puppetfile and specify the specific branch of the repository we want to test and include it in modulepath. The reasson behind my question is that we have testing and production stacks but want also to be able to easily use (some) testing branches in production, however if there's a mismatch between modules/site modules it will of course fail. Eh. Probably best to move it into control_repo
b
you can move everything into a single git repo, if that works with your permissions. sometimes certain teams should only access certain files and that's easy to implement with multiple repos
in that case you can have a Puppetfile in the control-repo that references the other repos
if you don't need multiple repos, merge all of them into the control-repo
a
Yeah. I guess it's either a single big repo or include a Puppetfile in control_repo which specifies a tag/sha for each module and for the site modules repositories. Maybe those are the two options. I'll have too look into for what is most suitable. Thanks for your input!
👍 1