Closed
Bug 1301401
Opened 9 years ago
Closed 9 years ago
Modify chain-of-trust implementation to conform to chainOfTrustVersion 1
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Assigned: pmoore)
References
Details
Attachments
(1 file)
This stems from https://bugzilla.mozilla.org/show_bug.cgi?id=1287112#c11:
To sum up, it looks like we have the following cot artifact changes across docker-worker, generic-worker, and scriptworker:
1. artifacts now looks like
"artifacts": {
"path/to/artifact": {
"sha256": "..."
}
...
}
2. Let's add a top level version at the top level. I'm open about the name.
"chainOfTrustVersion": 1
3. Rename 'extra' to 'environment'
"environment": {
"publicIpAddress": "12.34.56.78",
"privateIpAddress": "87.65.43.21",
"instanceId": "i123456789",
"instanceType": "c3.2xlarge",
"region": "us-west-2a"
}
4. Rename 'certificate.json.gpg' to 'chainOfTrust.json.asc'.
| Assignee | ||
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Commits pushed to master at https://github.com/taskcluster/docker-worker
https://github.com/taskcluster/docker-worker/commit/30584f88105ef4433f7edcf93c20b55deacaa61e
Bug 1301401 - updating to chainOfTrust version 1 format
https://github.com/taskcluster/docker-worker/commit/1a69b6ee6f3fc62832a70f9858e991da74393e34
Bug 1301401 - incorporated fixes suggested by garndt in PR review
https://github.com/taskcluster/docker-worker/commit/18f98605a1fbae37e73712cbcf576129a198a2e2
Merge pull request #249 from taskcluster/bug1301401
Bug 1301401 - updating to chainOfTrust version 1 format
Comment 3•9 years ago
|
||
Comment on attachment 8789686 [details] [review]
Github Pull Request for docker-worker
this has been merged but not yet deployed
Attachment #8789686 -
Flags: review?(garndt) → review+
Comment 5•9 years ago
|
||
Yup, this is all set.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(garndt)
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Docker-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•