[jira] [Resolved] (WHIMSY-54) Re-organise auth. by TLD?

["Shane Curcuru (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WHIMSY-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Curcuru resolved WHIMSY-54.
---------------------------------
    Resolution: Implemented

For development purposes, see doc on how to do this for tools:
https://github.com/apache/whimsy/blob/master/DEVELOPMENT.md#how-to-authenticateauthorize-your-scripts

> Re-organise auth. by TLD?
> -------------------------
>
>                 Key: WHIMSY-54
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-54
>             Project: Whimsy
>          Issue Type: Improvement
>            Reporter: Sebb
>
> Various parts of Whimsy require auth.
> At present this is done per app, which results in quite a complicated scheme.
> Also the auth conf is held in puppet whereas the app is in the Whimsy repo, so it's tricky to relate them.
> When adding a new app, the puppet config has to be updated as well.
> This can easily be overlooked.
> Maybe we should just use auth at the top level directory?
> This might require some apps to be moved, but would be much simpler to maintain going forward.
> The following levels are used currently:
> None
> ASF Committers
> ASF Members and Incubator PMC
> ASF Members and Officers
> ASF Members
> ASF Secretarial Team
> This suggests the following directories as a minimum:
> committers
> incubator
> officers
> members
> secretary



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)