The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/309d1b38ec90e588aed656c110ad6f97da8f736a

commit 309d1b38ec90e588aed656c110ad6f97da8f736a
Author: Vadim Shtayura <vadimsh@chromium.org>
Date: Wed Aug 23 22:21:05 2017

Dan, was this completed as part of the BigQuery work? Can you update the bug? Assigning to Dan to update. 

Yep!

luci-logdog-publisher service account key seems to be still deployed to swarming? https://chrome-internal.googlesource.com/infra/puppet/+/master/puppetm/opt/puppet/conf/nodes.yaml#504

Yeah I didn't un-deploy any credentials.

let's re-open this bug so we don't forget to undeploy them

Dan, are you going to un-deploy the credentials or someone else? 

I wasn't planning on it. It's not urgent, is it?

Looking a little deeper into it, the config linked in #4 doesn't seem trivial to modify to exclude *just* Swarming bots (see comment on linked line). ATM I'm tempted to just leave the creds there and remove them later with a bot-cleaning sweep. WDYT?

The important thing here is done - LogDog uses the auth context account.

I think this is done. Getting rid of luci-logdog-publisher account is blocked on moving off buildbot (where it is also used), so I consider it outside the scope of this task.