[jira] Commented: (INFRA-3160) Hook: Authorization

["Paul Joseph Davis (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993964#comment-12993964 ] 

Paul Joseph Davis commented on INFRA-3160:
------------------------------------------

I've reworked this same logic into a single hook for all pre-receive actions which can be seen at [1].

The last issue I'm running into for this is to figure out a way to keep the asf-authorization file up to date in a reasonable manner. I've contemplated cron or having the generation scripts push it out to git-wip-us, but I'm not familiar enough with policy/mechanics for either of those.

Any suggestions on this bit would be appreciated. For the time being I'll just let it run off a stale copy that I'll regenerate when someone complains.

> Hook: Authorization
> -------------------
>
>                 Key: INFRA-3160
>                 URL: https://issues.apache.org/jira/browse/INFRA-3160
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Paul Querna
>            Priority: Trivial
>         Attachments: pre-receive
>
>
> Task: Using a pre-receive hook, restrict the user to only write to a repository that they have group write access to.
> Groups are defined in LDAP, but we generally use a static file that is updated after ldap automatically, and it has been suggested that we re-use the svn authz file.
> If not using svn authz file format, write a script that exports to a file format usable by the hook, in addition to the hook script itself.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira