Closed Bug 1434369 Opened 7 years ago Closed 7 years ago

Time out Azure credential requests after <30s

Categories

(Taskcluster :: Services, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

We are getting H12's from Heroku when Azure takes >30s to respond to a credential request.  Let's manually time that out at less than 30s and return a suitable (5xx) error message to the client.
Let's put, say, a 6h expiration on that cache, too.
Commits pushed to master at https://github.com/taskcluster/taskcluster-auth

https://github.com/taskcluster/taskcluster-auth/commit/db83723f26a49103103679b87b0f6b552d36a300
Bug 1434369 - don't try to create tables / containers every time

This operation occasionally times out, so let's try to do it less often.

https://github.com/taskcluster/taskcluster-auth/commit/e438fc490d2b187e40f7673be9b5c59dac53a998
Merge pull request #130 from djmitche/bug1434369

Bug 1434369 - don't try to create tables / containers every time
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Authentication → Services
You need to log in before you can comment on or make changes to this bug.