+Valentyn Tymofieiev <[email protected]> might have an idea. On Mon, May 3, 2021 at 4:12 PM Chuck Yang <[email protected]> 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 work seems to > involve migrating off of google-apitools since this call [3] is not > supported by credentials objects emitted by google-auth. > > Does anyone have any experience/insights on how much work migrating > off of oauth2client would involve? I might be able to help out but > wanted to see a) if anyone is already looking at this and b) if there > are any hidden obstacles beyond needing to move from google-apitools > to the google-cloud-* libraries. Any pointers are appreciated! > > We're interested in this migration because of the need to use custom > token URIs for issuing service account tokens--it's supported by > google-auth but not oauth2client. > > [1] https://issues.apache.org/jira/browse/BEAM-7352 > [2] https://github.com/google/apitools/issues/225#issuecomment-434884589 > [3] > https://github.com/google/apitools/blob/v0.5.31/apitools/base/py/base_api.py#L266 > > Thanks! > Chuck > > -- > > > *Confidentiality Note:* We care about protecting our proprietary > information, confidential material, and trade secrets. This message may > contain some or all of those things. Cruise will suffer material harm if > anyone other than the intended recipient disseminates or takes any action > based on this message. If you have received this message (including any > attachments) in error, please delete it immediately and notify the sender > promptly. >
