Automaticlly map django groups to launchpad teams
Bug #503462 reported by
Thomas Bechtold
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
django-openid-auth |
Fix Released
|
Undecided
|
Thomas Bechtold |
Bug Description
Actually to use the lp-team<
For loco.ubuntu.com, the teams change from time to time and it's impossible (or stupid) to change the django settings.py file every time the teams change.
It would be cool if the mapping is automatic. So if there are 3 django-groups, theses group are mapped automaticlly to lp-teams (and both have the same name, then).
Related branches
lp:~toabctl/django-openid-auth/automatic_mapping_fixes_503462
- Elliot Murphy (community): Approve
-
Diff: 48 lines (+19/-0)2 files modifieddjango_openid_auth/auth.py (+9/-0)
django_openid_auth/views.py (+10/-0)
Changed in django-openid-auth: | |
assignee: | nobody → Thomas Bechtold (thomasbechtold) |
status: | New → Fix Committed |
Changed in django-openid-auth: | |
milestone: | none → 0.2 |
Changed in django-openid-auth: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thomas Bechtold wrote: ->django- group mapping, you have to define the variable OPENID_ LAUNCHPAD_ TEAMS_MAPPING {} for every group you want to map.
> Public bug reported:
>
> Actually to use the lp-team<
> For loco.ubuntu.com, the teams change from time to time and it's impossible (or stupid) to change the django settings.py file every time the teams change.
>
> It would be cool if the mapping is automatic. So if there are 3 django-
> groups, theses group are mapped automaticlly to lp-teams (and both have
> the same name, then).
>
> ** Affects: django-openid-auth
> Importance: Undecided
> Status: New
>
This seems to be reasonable. I also don't see any security impact since groups have no meaning until permissions are
assigned to them.
Perhaps the LAUNCHPAD_ TEAMS_MAPPING could be a way of restricting which groups get created so your database doesn't get
cluttered with groups.