Puppet and subversion
I've just started looking at using puppet to align our test environments with production (we can't use puppet to deploy to production unfortunately) as we often have quick bug fixes on production that aren't reflected on test. However our SVN trunk is kept up to date with the latest production code.
I basically need to just replicate files from our svn repository to all agents in certain locations, but looking at the puppet documentation they should be in "module" format and placed in the puppet modules folder (which I can get working manually). Our code isn't structured like that on SVN though and isn't really stored in any standard way (example below).
Can I just setup a cron job to svn checkout to a location on the puppet master and have a folder of manifest files that can be used that just point to the current svn structure rather than the enforced "module" standard?
Example svn, as you can see there isn't really a standard:
trunk -> monitoring_scripts -> scripts -> code here trunk -> monitoring_scripts -> config -> config here trunk -> library_files -> code here trunk -> another_component -> sh -> code here
So I'd want to checkout the svn repo so somewhere on the server and then have manifest files work off that "as is".
Sorry if this is too broad but any advise or general documentation to read around this topic would be greatly appreciated thanks.
Puppet master version : 2.7.26