Closed Bug 1083372 Opened 10 years ago Closed 9 years ago

Better document managing client credentials

Categories

(Tree Management :: Treeherder, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1225597

People

(Reporter: wlach, Unassigned)

References

Details

When getting running with treeherder-perf, I quickly ran into a situation where I wanted to submit stuff to the treeherder server myself, but did not know how to get the oauth keys necessary to do so. All I could find was some notes on running "manage.py export_project_credentials" in http://treeherder-service.readthedocs.org/en/latest/common_tasks.html#add-a-new-repository Chatting with :jeads and :camd, I found out that export_project_credentials just populates the project database tables with oauth keys, and exports them to a file called 'treeherder/etl/data/credentials.json' (which you can later share with other people). Let's document this in treeherder-service (and maybe point to it from the treeherder-client README.md?) so that people can self-serve an answer to this question in the future. :)
Blocks: 1072681
OS: Linux → All
Priority: -- → P3
Hardware: x86_64 → All
No longer blocks: 1072681
Component: Treeherder → Treeherder: Docs & Development
Priority: P3 → P4
Blocks: 1196191
Changing this to be about registering a new set of (hawk) client credentials.
Summary: Better document managing oauth keys → Better document managing client credentials
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Component: Treeherder: Docs & Development → TreeHerder
You need to log in before you can comment on or make changes to this bug.