Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

download artifacts with temp_queue if possible

Open
#426 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Locate the artifact download path that currently uses queue, then compare how temp_queue is made available to tasks needing private artifacts. The work is done when those downloads use temp_queue and no longer require private-artifact access for the worker clientId; check the existing artifact-related tests if available.

Written by the indexing model from the issue text.

Description

We currently download artifacts with queue, which uses the worker creds. This means for private artifacts, the worker clientId needs to have access to those private artifacts.

The temp_queue will be given access to private artifacts for those tasks that need them. So if we download artifacts with that, we no longer need to add private artifact support to the worker clientId. Let's do that.

Dominant language
Python
Stars
5
Forks
40
Avg merge
22h 14m
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla-releng/scriptworker

All issues in mozilla-releng/scriptworker

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.