taskcluster/taskcluster-queue — pull request #20 by jonasfj (2014-08-03 00:52:30+00:00)
Title: Using schedulerId

This PR does:

* Add `schedulerId` and `taskGroupId` to all tasks and use them in scopes for `rerunTask` and `scheduleTask`.
* Adds forceSSL (this part might already be deployed)
* Renamed a few scopes, specifically:
* Remove HTTP verb, e.g. `queue:put:task:...` -> `queue:create-task:...`
* Remove `queue:` from roles, e.g. `queue:assume:worker-id:...` -> `assume:worker-id:...`

The scope renaming was just because I realized after our talks that we would never want to give anybody a scope such as `queue:get:*` or `queue:put:*` (specially, since it would make no sense with `queue:post:*`).
So shorter scopes are better, and clutters the docs and implementation less...

I don't see many use-cases where we want to reuse roles... But if/when we put an API on the provisioner, we might want workers to be able to prove their workerId using `assume:worker-id:/`.
So removing the `queue:` prefix made sense.. I see no reason roles like this shouldn't be global.

I haven't deployed the breaking changes.... I'm not sure a review is worth the tests pass... If you want to see anything checkout `v1.js` and see if any of the scope names bother you :)
Otherwise I just we merge so I can start working the scheduler... which will need a few changes to use this (mostly deleting code, we no longer need).