Repository navigation
feat(run-task): fetch secrets listed in RUN_TASK_SECRETS - #1105
Conversation
|
This adds the ability to fetch a Github app installation access token in As you might guess from the implementation, the intent here is to also support fetching Taskcluster secrets using this mechanism (a feature I've long meant to implement). But I'll tackle that part separately. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1105 +/- ##
==========================================
+ Coverage 80.00% 80.13% +0.13%
==========================================
Files 134 134
Lines 14190 14288 +98
Branches 1645 1654 +9
==========================================
+ Hits 11352 11450 +98
Misses 2399 2399
Partials 439 439 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
RUN_TASK_SECRETS is a JSON list of secrets for run-task to fetch before checkout. The first type, github-repo-token, requests a GitHub App installation token from Taskcluster's auth service and exports it to an environment variable, GITHUB_TOKEN by default. Tokens are also kept in memory so run-task can authenticate its own GitHub requests.
01cbd8b to
785504a
Compare
|
You can see this working here: |
RUN_TASK_SECRETS is a JSON list of secrets for run-task to fetch before checkout. The first type, github-repo-token, requests a GitHub App installation token from Taskcluster's auth service and exports it to an environment variable, GITHUB_TOKEN by default. Tokens are also kept in memory so run-task can authenticate its own GitHub requests.