To pick up the new 'require_host_type' config option: https://github.com/jeads/datasource/issues/21 ...so we can enforce that we've set host_type everywhere.

Commit pushed to master at https://github.com/mozilla/treeherder-service https://github.com/mozilla/treeherder-service/commit/a9188108ec1d31e32d680907a5609e49e71de97f Bug 1125585 - Update datasource to fab643e0d5 To pick up the new require_host_type config option: https://github.com/jeads/datasource/pull/22 Also includes: https://github.com/jeads/datasource/pull/17

We need to deploy the newer datasource on stage/prod, updating the in-repo manifest isn't sufficient on it's own, since we don't automate dependency installation.

Waiting on https://github.com/jeads/datasource/pull/24

Comment on attachment 8554236 [details] Update datasource to fab643e0d5 (setting flag just so this appears in the correct section on bugzilla-todos, given there will be a part 2 required)

Commit pushed to master at https://github.com/mozilla/treeherder-service https://github.com/mozilla/treeherder-service/commit/694dc0dd10338959f555be634baf3383689dd45e Bug 1125585 - Update datasource to 2f09c9cc87 To pick up the version number bump. This doesn't change the contents of vendor/datasource/ so in theory shouldn't be necessary. However prod pip installs the requirements in pure.txt when it shouldn't, and the vendor directory is later in python.path than site-packages, so we end up using the version installed globally. Unfortunately some of the nodes have an older version of datasource installed, but without the version bump it's hard to tell which.

Given bug 1134740 will make us use the vendor version in preference to the globally installed one, we no longer need to remove datasource globally here, but can leave that to the cleanup in bug 1070470.