Closed
Bug 1459075
Opened 7 years ago
Closed 6 years ago
[tracker] All services must support TASKCLUSTER_ROOT_URL
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bstack, Assigned: bstack)
References
Details
All services must have their config allow for setting a rootUrl for all uses of taskcluster-client via an environment variable called TASKCLUSTER_ROOT_URL. This will allow the services to integrate into whatever cluster they are deployed in.
Docs for passing rootUrl to taskcluster-client are in [0]. If the rootUrl is null, it will fall back to talking to the normal taskcluster cluster for now.
Note: Currently the env var it listens for is TASKCLUSTER_ROOT there. Ignore this. We should set this value explicitly when we instantiate the taskcluster-client.
[0] https://github.com/taskcluster/taskcluster-client#configuring-api-root-url
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Blocks: redeploy-firefox-ci
Comment 2•6 years ago
|
||
At the moment, we're not planning to move aws-provisioner, so this is done.
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Redeployability → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•