[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: wild card support for authz

From: Andy Levy <andy.levy_at_gmail.com>
Date: Thu, 2 Dec 2010 10:43:40 -0500

On Thu, Dec 2, 2010 at 10:36, Kriparam Faraday <kriparam_at_gmail.com> wrote:
> Hi,
> I am not sure if this feature is part of the current 1.6 release. We have
> created groups based on their work function(like developers, QA etc...). The
> developers get RW access to everything including the documentation folder
> and the source folder. The QA group gets RW in the documentation folder but
> gets only R access in the source code. This works fine, until someone
> decides to branch off or tag something from the trunk. I want to know if we
> can use some wildcards to give QA default access into all the documentation
> folders. for example:
> [<proj_name>:/branches/*/docs]
> @dev = rw
> @ qa = rw
> [<proj_name>:/branches/*/source]
> @dev = rw
> @ qa = r
> Will this work? or are there any other way to implement it?

Authz does not support wildcards. If you need to restrict write access
via wildcards, svnperms.py can be installed as a pre-commit hook
script to provide more control over your access.
Received on 2010-12-02 16:44:59 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.