1056052 - Document how to give a user sheriffing permissions (is_staff) in development

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder, enhancement, P3)

Description

[Sylvestre Ledru [:Sylvestre]]

Because I am lazy, I think it would be nice to have the command to create a new user included on this page:
http://treeherder-service.readthedocs.org/en/latest/installation.html

mdoglio told me that it should be:
manage.py createsuperuser

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I got the following code from Mauro, which let me add an existing user (as logged in via persona) to the staff group:

from django.contrib.auth.models import User
u = User.objects.get(email="[e-mail]")
u.is_staff = True
u.save()

Comment 2

[Jonathan French (:jfrench)]

Attachment: treeherder-PR631

Please see above PR for status and review.

Comment 3

[Jonathan French (:jfrench)]

I haven't had any chance to get back to this (additional request to create a promotesuperuser django command); so I'll leave the bug open for now and folks can use the closed PR for reference if they need it https://github.com/mozilla/treeherder/pull/631.

Comment 4

[Sylvestre Ledru [:Sylvestre]]

Should we wontfix that?
thanks

Comment 5

[Ed Morley [:emorley]]

I think this (or some variation of it) is still relevant. We should either:
1) Document how to test features during development as a fake admin
2) Make all users during development admins or provide a "sudo" mode to toggle

Also worth noting is that once bug 1273092 is fixed, people who belong to the relevant groups will automatically get admin permissions when developing on Treeherder, though that doesn't help contributors, who would still need (1) or (2).

Comment 6

[Ed Morley [:emorley]]

Wontfix since:
* it's now possible to use auth when doing UI-only development by pointing at stage/prod (which `createsuperuser` won't help with)
* since the bug was filed fewer things use is_staff (pretty much only perf sheriffing and some cancel-job buildbot-isms that will be going away), since we removed the exclusions profile/django admin/...
* bug 1273092 will be making user permissions use the LDAP groups
* if we did want to fix this, the better fix would be to make all vagrant users have admin, rather than having to add Yet More Setup Steps.