wild card support for authz

[Kriparam Faraday <kr...@gmail.com>]

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?

Thanks,
Kripa

Re: wild card support for authz

[Johan Corveleyn <jc...@gmail.com>]

On Thu, Dec 2, 2010 at 4:43 PM, Andy Levy <an...@gmail.com> wrote:
> On Thu, Dec 2, 2010 at 10:36, Kriparam Faraday <kr...@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.

You may be interested to know that there is an open feature request
about this in the issue tracker:
http://subversion.tigris.org/issues/show_bug.cgi?id=2662 - authz with wildcards

Cheers,
-- 
Johan

Re: wild card support for authz

[Andy Levy <an...@gmail.com>]

On Thu, Dec 2, 2010 at 10:36, Kriparam Faraday <kr...@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.