webservice allows new_project to set registrant but not owner

Bug #606085 reported by James Westby
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Hi,

new_project allows registrant to be set over the webservice, but owner is
forced to REQUEST_USER. This is backwards to what I thought I saw elsewhere,
is it intentional?

Thanks,

James

Revision history for this message
James M.Kuhn (jmkuhn007) wrote :

this was not intentional. I lot going on atm personal life. I have been trying to sign code of conduct. I just did this all backwards

Revision history for this message
Curtis Hovey (sinzui) wrote :

This is certainly the opposite of what is intended.
1. registrant must be the request user
2. owner can be the request user, but I think a better behaviour is to allow users to pass the owner. Users are very good a shooting themselves in the foot during registration, so I ponder if the API should have an extra argument to make someone else the owner.

Changed in launchpad-registry:
status: New → Triaged
importance: Undecided → Low
Curtis Hovey (sinzui)
tags: added: api
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.