Open Bug 1598444 Opened 5 years ago Updated 5 years ago

taskcluster-worker-runner should accept a config for what secret to read.

Categories

(Taskcluster :: Workers, enhancement)

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

Tracking

(Not tracked)

People

(Reporter: tomprince, Unassigned)

References

Details

The current primary use of worker-pool secrets, is to pass the stateless-hostname secret to docker-worker; in general, it seems that the worker-config stored in secrets typically isn't worker-specific, but rather shared between a bunch of workers.

Rather than requiring someway to create and keep up-to-date all those worker secrets, it should be possible to have a single secret that is read by all the relevant workers.

I'm not sure the dependency is necessary; currently I mainly want this for docker-worker, so I'd be happy to have this feature, even if it means there isn't parity between the two worker types here, temporarily.

That "temporary" is usually "permanent", so I'd like to try to get ahead of the divergence this time, if possible.

You need to log in before you can comment on or make changes to this bug.