Closed Bug 1434393 Opened 7 years ago Closed 7 years ago

Give Sarah access to the prod read-only replica

Categories

(Tree Management :: Treeherder: Infrastructure, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

To help test the frontend + new API endpoints against prod failure classification data. I'll create an account using: https://treeherder.readthedocs.io/admin.html#direct-database-access
I've created an account with read-only permissions and I'll send the credentials to you separately. To use them export the updated DATABASE_URL inside Vagrant using something like: `export DATABASE_URL='mysql://USER:PASSWORD@treeherder-prod-ro.REDACTED.us-east-1.rds.amazonaws.com/treeherder'` ...then to reset back to the local DB either log out/in of vagrant, or else run `source vagrant/env.sh`. Note: The user GRANTS don't give read access to all of the auth_user table, so queries against that might fail unless limited to just the "username", "email" and "id" fields (Django loads all fields by default). However unless the new UI has a "who classified this" column on the details view, I guess this shouldn't affect you)
Blocks: 1367362
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Summary: Give Sarah to the prod read-only replica → Give Sarah access to the prod read-only replica
I've just added the extra permissions mentioned in the meeting, using: GRANT SELECT ON treeherder.auth_user to 'sclements';
You need to log in before you can comment on or make changes to this bug.