Dustin J. Mitchell [:dustin] (he/him) Reporter
	Description • 7 years ago

I'm not sure what those are, but grepping for TASKCLUSTER_ in docker-worker could probably reveal them.  They should also be documented here
  https://docs.taskcluster.net/reference/workers/docker-worker/environment

	Chris Cooper [:coop] (he/him)
	Comment 1 • 6 years ago

Pete: worker consolidation obviates this. Should this be duped forward or closed?

	Dustin J. Mitchell [:dustin] (he/him) Reporter
	Comment 2 • 6 years ago

These could be at https://docs.taskcluster.net/docs/manual/design/env-vars now

	Simon Sapin (:SimonSapin)
	Comment 3 • 6 years ago

That document starts with:

> Taskcluster defines several environment variables, 

Which feels very vague to me. Defines where? Does this mean that worker implementations like docker-worker and generic worker, when they are given arbitrary scripts/commands to run through a task definition, are expected to define these variables for use by those scripts/commands?

> TASKCLUSTER_CLIENT_ID is the clientId to use for Taskcluster API calls. 

Is this for the purpose of making API calls from tasks? How does this compare with the `taskclusterProxy` feature (which AFAIU does not require authentication) of docker-worker and generic-worker?

	Dustin J. Mitchell [:dustin] (he/him) Reporter
	Comment 4 • 6 years ago

It defines them right there in the very next line :)

But yes, that document could be more explicit about when these variables are provided, and when they are expected.  Bug 1511457.