Thanks folks, I did take a look at the change and swapping to the
google-cloud-* libraries looks like a major refactor.
I did get something working by adding a shim so that the existing
vendored libraries can work with the google-auth credential objects,
similar to Luke's second point. Is this par
Thanks, Chuck for looking into this. We explored switching to
google-cloud-* python libraries for Dataflow runner purposes, and
encountered several issues related to dependency management of these
libraries in Google-internal repository, which were difficult to address
just in Beam plane without ve
I did something very similar during the Dataflow Java 1.x to Beam Java 2.x
migration. The work boiled down to:
* swapping to a different library to get the application default
credentials (including fixing upstream bugs at Google and improving some
documentation)
* swapping existing API calls to us
+Valentyn Tymofieiev might have an idea.
On Mon, May 3, 2021 at 4:12 PM Chuck Yang wrote:
> Hi Beam devs,
>
> I saw there has been some previous discussion [1][2] around removing
> the deprecated oauth2client dependency and using the supported
> google-auth dependency instead. A portion of this
Hi Beam devs,
I saw there has been some previous discussion [1][2] around removing
the deprecated oauth2client dependency and using the supported
google-auth dependency instead. A portion of this work seems to
involve migrating off of google-apitools since this call [3] is not
supported by credent
