This is a continuation of #45.
generate code for taskcluster.sync.*
fix genCode docstring newlines
remove signUrl support from the generated code
Copy exponential backoff from go client
add buildUrl back into baseclient, with routes instead of urls, and q…
…uery string support
avoid defining ROUTING_KEY_WHITELIST twice
argumentString to a single function
docstringify -> typesetDocstring
FakeGenerated -> createFakeApi
@jhford how does escapewindow@92d8006 look for dual integration tests?
I'm leaning towards splitting that out into a test_integration.py, but I don't feel strongly about it.
integration tests cover both runtime- and buildtime- generated Auth
I thought I should mention, since I would wonder if I were in your position:
I wanted to have TestRuntimeAuthentication inherit TestAuthentication, only replacing the taskcluster.Auth class with a createApiClient class. That would be a lot neater and simpler. However, when I did that, nosetests didn't run any tests for TestRuntimeAuthentication.
Maybe there's a trick I don't know, but this was the way I got tests to run for both TestRuntimeAuthentication and TestBuildtimeAuthentication.
Looks good! It might be possible to generate the test classes programmatically using the type function, (see createApiClient as example), but I don't think that's blocking. I'd like to take one more overall look at this a little later, but I don't expect there to be anything major.
Thanks for working on this!
@jhford, have you had a chance to take another look yet?
Yep! Looks good. I'm going to merge this but hold off on releasing a new major version to send an email suggesting that users of the client library try it out and let us know if there are issues for them.