Creating private PPAs on public teams requires admin-level privileges

Bug #1012135 reported by Jonathan Lange
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jonathan Lange

Bug Description

At the moment, creating private PPAs on public teams requires admin-level privileges. One must be either in ~admins or ~commercial-admin. These privileges far exceed the ability to create private PPAs.

We (Canonical Consumer Applications) would like to create private PPAs over the API as part of an automated process involving developer.ubuntu.com. We do *not* want our bot having admin privileges.

Related branches

Revision history for this message
Jonathan Lange (jml) wrote :

Perhaps related to bug 724920.

tags: added: p3a ppa
Curtis Hovey (sinzui)
tags: added: entitlement
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Curtis Hovey (sinzui)
Changed in launchpad:
assignee: nobody → Jonathan Lange (jml)
Revision history for this message
Julian Edwards (julian-edwards) wrote :

To save casual observers from diving into the diff, the branch that fixes this allows people with commercial subscriptions to create private PPAs.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
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.