Open Bug 1492274 Opened 2 years ago Updated 2 years ago

Clean up action_scope

Categories

(Firefox Build System :: Task Configuration, task, P5)

task

Tracking

(Not tracked)

People

(Reporter: dustin, Unassigned, Mentored)

References

Details

The in-tree .taskcluster.yml contains:

# when all actions are hooks, we can calculate this directly rather than using a variable

and ci-admin's in_tree_actions.py contains:

# Calculated repo_scope.  This is based on user input (the repository),
# but the hooks service checks that this is satisfied by the 
# `hook-id:<hookGroupId>/<hookId>` role, which is set up above to only
# contain scopes for repositories at this level. Note that the 
# action_perm is *not* based on user input, but is fixed in the 
# hookPayload template.  We would like to get rid of this parameter and 
# calculate it directly in .taskcluster.yml, once all the other work
# for actions-as-hooks has finished
'repo_scope': 'assume:repo:${payload.decision.repository.url[8:]}:action:' + action.action_perm,

Let's clean that up once release-promotion is a hook.  This will involve coordinated changes in ci-admin, scriptworker, and the in-tree code.
Mentor: dustin
Severity: normal → enhancement
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.