Skip to content

docs: add some info about CoT verification expectations w.r.t decisio… #600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add some info about CoT verification expectations w.r.t decisio… #600

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/cot_verify.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,4 +64,13 @@ Scriptworker:

Once all verification passes, it launches the task script. If chain of trust verification fails, it exits before launching the task script.

Extra data and assumptions
~~~~~~~~~~~~~~~~~~~~~~~~~~

Some of the information necessary for rebuilding decision task definitions can't be independently re-generated at verification time; for these cases, we rely on additional data in the original task definition itself. That means the project's `.taskcluster.yml` needs to store that information for CoT to find it, and that `.taskcluster.yml` shouldn't make security-relevant decisions based on it. These bits are:

- in action tasks, `task.extra.action.context` should contain the action's `taskGroupId`, `taskId` and `input`, plus any other bits of context used by `.taskcluster.yml`, e.g. `clientId`; `task.extra.parent` should contain its parent task's `taskId` (pointing at either a decision task or another action task).
- in decision tasks for cron jobs, `task.extra.cron` should be a copy of the `cron` object passed to the task, containing `task_id`, `job_name`, `job_symbol` and `quoted_args`
- in all cases, `task.extra.tasks_for` contains the `tasks_for` value.

.. _json-e: https://github.com/taskcluster/json-e