Skip to content

Commit 3410301

Browse files
authored
actions: remove hardcoded gecko trust domain from retrigger-decision action (#458)
1 parent 3b88079 commit 3410301

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

src/taskgraph/actions/retrigger.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,9 @@ def retrigger_decision_action(parameters, graph_config, input, task_group_id, ta
6565
# absolute timestamps relative to the current time.
6666
task = taskcluster.get_task_definition(task_id)
6767
task = relativize_datestamps(task)
68-
create_task_from_def(slugid(), task, parameters["level"])
68+
create_task_from_def(
69+
slugid(), task, parameters["level"], graph_config["trust-domain"]
70+
)
6971

7072

7173
@register_callback_action(

src/taskgraph/actions/util.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,15 +90,15 @@ def fetch_cron(task_id):
9090
return (decision_task_id, full_task_graph, label_to_taskid)
9191

9292

93-
def create_task_from_def(task_id, task_def, level):
93+
def create_task_from_def(task_id, task_def, level, trust_domain):
9494
"""Create a new task from a definition rather than from a label
9595
that is already in the full-task-graph. The task definition will
9696
have {relative-datestamp': '..'} rendered just like in a decision task.
9797
Use this for entirely new tasks or ones that change internals of the task.
9898
It is useful if you want to "edit" the full_task_graph and then hand
9999
it to this function. No dependencies will be scheduled. You must handle
100100
this yourself. Seeing how create_tasks handles it might prove helpful."""
101-
task_def["schedulerId"] = f"gecko-level-{level}"
101+
task_def["schedulerId"] = f"{trust_domain}-level-{level}"
102102
label = task_def["metadata"]["name"]
103103
session = get_session()
104104
create.create_task(session, task_id, label, task_def)

0 commit comments

Comments
 (0)