If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET not set on Heroku treeherder-prod

RESOLVED FIXED

Status

Tree Management
Treeherder: Infrastructure
P1
normal
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: emorley, Assigned: camd)

Tracking

Details

(Reporter)

Description

a year ago
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

a year 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

a year ago
Assignee: nobody → cdawson
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
(Reporter)

Comment 2

a year 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.