Closed
Bug 1306155
Opened 8 years ago
Closed 8 years ago
GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET not set on Heroku treeherder-prod
Categories
(Tree Management :: Treeherder: Infrastructure, defect, P1)
Tree Management
Treeherder: Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: camd)
References
Details
GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET aren't set on the Heroku treeherder-prod app. Are we using different values for each environment? If so, could you generate some new ones for Heroku prod and set them? Otherwise I can just copy those from Heroku stage.
Thanks :-)
Flags: needinfo?(cdawson)
Assignee | ||
Comment 1•8 years ago
|
||
I have separate ones for stage and prod, which I think could just be transferred over from the scl3 values. I've updated them on heroku prod now.
Flags: needinfo?(cdawson)
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → cdawson
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•8 years ago
|
||
Ah I was confused since SCL3 stage wasn't using the same set as Heroku stage (it turns out it was using SCL3 prod's).
I've now also changed Heroku stage's to match SCL3 stage's.
You need to log in
before you can comment on or make changes to this bug.
Description
•