Puppet Modules

Strategy

After pondering for quite some time, I decided to choose the following strategy

• Use a git repository for each module using git submodule
• If an existing can be used, don’t reinvent the wheel and clone it directly (remember that git submodule references a concrete commit of the referenced repository)
• If you have to change anything. Create a new repository on github with the changes. Names will be “puppet-<modulename” and push your changes there
• For new modules create a new github repository.

Structure for main checkout (per customer) is probably something like
- customer
- customer/modules/<whatever_he/she_needs>
- customer/elexis-common (needed?, e.g. for bootstrapping, simple-cdd?)
???

open questions

• Do I need development/test/production branches in each module?
• Is it sufficient just to have different branches on the main module?