After a very serious discussion with myself :)
I found a solution/workaround which my colleagues are satisfied with.
Because we want to use puppet in push only mode, every admin has to login to
the puppetmaster anyway.
So instead of trying to get a post commit hook working from our subversion
s
On 04/20/2011 09:55 AM, Andreas Paul wrote:
> Do you suggest calling that rsync in the post commit hook?
> That is not possible as the svn hook script is run by a httpd user
> without any permissions and granting him any permission just for that
> hook script would be hard to justify.
Hi,
doesn't
Do you suggest calling that rsync in the post commit hook?
That is not possible as the svn hook script is run by a httpd user without
any permissions and granting him any permission just for that hook script
would be hard to justify.
--
You received this message because you are subscribed to th
> The puppetlabs wiki page uses a simple svn update /etc/puppet in the
> post-commit hook script, but that implies that the SVN server is on the
> same machine as the puppetmaster, which is not the case in my environment.
Hi,
you could fall back to something less elegant like "svn update + rsync
Hello there,
I'm trying to get SVN working with puppet, but what I need to do is a remote
svn update on the puppetmaster server, so that puppet uses the latest
configuration.
The puppetlabs wiki page uses a simple svn update /etc/puppet in the
post-commit hook script, but that implies that the
