Closed Bug 1519277 Opened 7 years ago Closed 7 years ago

Replace all continuationtoken uses in services with proper Entity.continuationToken

Categories

(Taskcluster :: General, enhancement)

Product:
Taskcluster
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bstack, Unassigned)

Details

Currently in at least the auth service we have some manually created query regex for continuation tokens. We should replace them with proper ones.

This will require inventing our own continautionToken format and encoding/decoding from that format to the (unkown) Azure format. So basically all we could do is say "it's base64" in the regexp. I'm not sure that's a big win, especially if we will later be converting to postgres. Could we WONTFIX?

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.