Closed Bug 1428420 Opened 7 years ago Closed 6 years ago

Update node client for r14y

Categories

(Taskcluster :: Services, enhancement)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bstack, Assigned: dustin)

References

Details

Explained in bug 1428417.
Assignee: nobody → bstack
Status: NEW → ASSIGNED
Blocks: 1460012
Assignee: bstack → pmoore
Pete: ETA?
Flags: needinfo?(pmoore)
I think dustin will be implementing this based on RFC 128.
Assignee: pmoore → dustin
Flags: needinfo?(pmoore)
Depends on: 1505404
I'm not sure what section 4.7 means, in the final analysis. What we discussed is different from what it says. Which of TASKCLUSTER_ROOT_URL, TASKCLUSTER_CLIENT_ID, TASKCLUSTER_ACCESS_TOKEN, and TASKCLUSTER_CERTIFICATE should the client automatically handle?
Flags: needinfo?(pmoore)
I've moved that to a new RFC, and when that's decided then we can file new bugs as necessary to implement it. Otherwise, I think the changes needed here are done.
Flags: needinfo?(pmoore)
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Component: Redeployability → Services
You need to log in before you can comment on or make changes to this bug.