Ask Your Question

Risk of Changing Permissions When using SVN on Puppet Master Configs

asked 2013-05-04 23:05:55 -0600


I an in the process of putting my Puppet Master configs into version control using SVN. I'm concerned about file permission and ownership changes as a result of this. SVN does not store permissions. How does one safely use SVN with puppet configs in terms of permissions of the config files? Our existing configs have mixed ownership in the config files, including some owner by root and some by the puppet user.



edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2013-05-05 01:04:28 -0600

jonn gravatar image

I think the usual way to do this is to run a script post-checkout to fix up the permissions according to a configuration file (or create a wrapper for svn to do the same job, if that fits your workflow better).

If you want to try and maintain the ownership/permission information within the subversion repository instead of within a config file, you could try asvn, which uses custom svn properties to squirrel away the extra information.

edit flag offensive delete link more


Good tips. I tried asvn but to no avail getting it to act on custom properties. I've found no documentation for it. I think I'll write a post ...(more)

Cornellio gravatar imageCornellio ( 2013-05-05 21:47:31 -0600 )edit

answered 2013-05-07 17:59:48 -0600

updated 2013-05-09 00:34:12 -0600

I believe the files within modules and manifests on the puppetmaster(s) should be owned by the user deploying your code from svn (ideally not root), we use 'deploy'.

It's the responsibility of the modules to make sure the files on the puppet agent have the right ownership and permissions, see an example

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: 2013-05-04 23:05:55 -0600

Seen: 145 times

Last updated: May 09 '13