Automaticlly map django groups to launchpad teams

Bug #503462 reported by Thomas Bechtold
8
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<->django-group mapping, you have to define the variable OPENID_LAUNCHPAD_TEAMS_MAPPING {} for every group you want to map.
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

Revision history for this message
John O'Brien (jdobrien) wrote : Re: [Bug 503462] [NEW] Automaticlly map django groups to launchpad teams

Thomas Bechtold wrote:
> Public bug reported:
>
> Actually to use the lp-team<->django-group mapping, you have to define the variable OPENID_LAUNCHPAD_TEAMS_MAPPING {} for every group you want to map.
> 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.

Revision history for this message
Thomas Bechtold (toabctl) wrote :

i don't want to create groups automaticly. i want to get the membership for a user of all exisiting groups in the django-db.

Changed in django-openid-auth:
assignee: nobody → Thomas Bechtold (thomasbechtold)
status: New → Fix Committed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Will the fix be rolled into a new release? :)

Revision history for this message
Elliot Murphy (statik) wrote : Re: [Bug 503462] Re: Automaticlly map django groups to launchpad teams

On Mon, Jan 11, 2010 at 9:36 AM, Daniel Holbach
<email address hidden>wrote:

> Will the fix be rolled into a new release? :)

Yes, I hope it will be this week.
--
Elliot Murphy | https://launchpad.net/~statik/

Revision history for this message
Daniel Holbach (dholbach) wrote :

Like... today? :-D

Revision history for this message
Elliot Murphy (statik) wrote :

On Friday we found some strange 500 errors when trying to use the
latest version of this code in production on ubuntu one. We're
investigating now, I think it would be better to fix this before
cutting a new release. Soon I hope!

On Mon, Jan 18, 2010 at 9:23 AM, Daniel Holbach
<email address hidden> wrote:
> Like... today? :-D
>
> --
> Automaticlly map django groups to launchpad teams
> https://bugs.launchpad.net/bugs/503462
> You received this bug notification because you are a member of django-
> openid-auth developers, which is the registrant for django-openid-auth.
>

--
Elliot Murphy | https://launchpad.net/~statik/

Revision history for this message
Dave Walker (davewalker) wrote :

@Elliot, Were these django side or launchpad side? Oddly, using this I encountered some odd LP-OOP's that were inconsistent and unable to reliably reproduce.

Revision history for this message
Elliot Murphy (statik) wrote :

the errors we were seeing were django side (i think). aquarius has
tracked it down to something that changed in revision 45 of
django-openid-auth. now to figure out why :)

On Mon, Jan 18, 2010 at 10:29 AM, Dave Walker <email address hidden> wrote:
> @Elliot, Were these django side or launchpad side?  Oddly, using this I
> encountered some odd LP-OOP's that were inconsistent and unable to
> reliably reproduce.

--
Elliot Murphy | https://launchpad.net/~statik/

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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.