We need credentials for mozharness to be able to use TC to upload files to s3. I've already created a buildbot user in https://tools.taskcluster.net/auth/ and added 'taskcluster_clientId' and 'taskcluster_accessToken' into hiera. This bug will track adding them into BuildSlaves.py so that mozharness can use them from oauth.txt

Self note (for seamonkey) Well need to add these secrets to our puppet even if unused to avoid breaking startup

template in buildbot-configs

Actual puppet changes to pull the credentials from hiera. Please double-check hiera to make sure I didn't hose it up :)

Comment on attachment 8537451 [details] [diff] [review] bb-configs-taskcluster-creds https://hg.mozilla.org/build/buildbot-configs/rev/2bc473e710b9

Comment on attachment 8537452 [details] [diff] [review] puppet-taskcluster-creds default: remote: https://hg.mozilla.org/build/puppet/rev/29f074e457d6 production: remote: https://hg.mozilla.org/build/puppet/rev/875351727cdc

In production: https://hg.mozilla.org/build/buildbot-configs/rev/2bc473e710b9

We need separate credentials for try builds. I've created a new taskcluster auth and put the keys in hiera as try_taskcluster_clientId / try_taskcluster_accessToken

I think we are set here - the credentials still need to be copied in for try builds, but that's bug 1119500.