Closed Bug 1194807 Opened 9 years ago Closed 9 years ago

create and deploy taskcluster credentials for release runner dev

Categories

(Release Engineering :: Release Automation: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

Attachments

(1 file)

We're getting close to wanting to being able to create task graphs with it, and we'll need release runner to have credentials to be able submit it!
I created credentials called "release runner dev", and granted them the following scopes:
    queue:*
    docker-worker:*
    scheduler:*
    signing:format:gpg
    signing:format:mar
    signing:cert:dep-signing


...which are most of the things listed in https://github.com/rail/releasetasks/blob/master/releasetasks/templates/release_graph.yml.tmpl right now. I explicitly didn't include signing:cert:release-signing or docker-worker:feature:balrogVPNProxy, because those are only needed for production balrog/signing, and we don't want dev to be able to do that.
Attachment #8648169 - Flags: review?(rail) → review+
Comment on attachment 8648169 [details] [diff] [review]
deploy tc creds in release runner config

I added the necessary secrets to Hiera and checked this in.
Attachment #8648169 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: