Closed
Bug 1321561
Opened 8 years ago
Closed 8 years ago
Can't specify TLS certificates to docker-cloud services
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Unassigned)
References
Details
..or just get off docker cloud.
The "Classic UI" (the one that works) is ending today, and is already broken.
The new UI doesn't allow input of multiline environment variables, which means we need a new way to specify the TLS key to the services we have there. Thankfully only one of the three services we host there, statsum, uses TLS (the others are cloud-mirror and stateless-dns).
I submitted a service request regarding entering such environment variables.
|
Reporter | |
Comment 1•8 years ago
|
||
I don't think this is especially urgent (but I'm checking). That said, maybe now is the time to move statsum to Heroku? Jonas, any reason not to, or that it would be difficult?
Flags: needinfo?(jopsen)
|
|
Reporter | |
Comment 2•8 years ago
|
||
Well, shoot, we have to do this today, as the cert will get revoked soon after that.
Admittedly, most clients of statsum are probably not checking revocation lists, and anyway an outage of statsum is not the end of the world, but at any rate this is fairly urgent.
|
|
Reporter | |
Comment 4•8 years ago
|
||
K, Jonas changed this to not need multiline inputs.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•