Closed Bug 1375201 Opened 7 years ago Closed 6 years ago

[docker-worker] Remove support for reading secrets from AWS worker type definition

Categories

(Taskcluster :: Workers, enhancement)

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

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1375190

People

(Reporter: pmoore, Unassigned)

References

Details

Only do this, once the provisioner no longer supports the feature, i.e. when 1375197 is resolved fixed.
Found in triage. Pete: you were going to do something with this batch of bugs, IIRC.
Flags: needinfo?(pmoore)
I haven't had bandwidth to work on this, but yes we would certainly like to get to it.
Flags: needinfo?(pmoore)
This work does not directly block the worker manager's deployment (bug 1478941), but does block it from being used in production. Worker Manager will only support generation of taskcluster credentials and will have no facilities for storing secrets directly.
See Also: → 1478941
(In reply to Pete Moore [:pmoore][:pete] from comment #0) > Only do this, once the provisioner no longer supports the feature, i.e. when > 1375197 is resolved fixed. I think this dependency is reversed. We cannot remove secrets from the provisioner until they are no longer being read by workers.
Blocks: 1375197
No longer depends on: 1375197
Component: Docker-Worker → Workers
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.