Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: use the official Google API python library #23

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

paulRbr
Copy link

@paulRbr paulRbr commented Nov 19, 2020

Description of change

These changes will make use of the official google-api-python-client
library instead of relying on manual HTTP requests.

There are two main advantages of these changes:

  • the Tap doesn't need to worry about the Google API interaction
    details as its hidden away by the Google official lib.
  • We can use the authentication helpers from the lib to ease the
    credentials management for the user. In that way the current PR
    implements two auth mean:
    • installed OAuth client authentication
    • Service Accounts authentication.

Manual QA steps taken

  • individual testing of each google api call
  • tested in --discover mode
  • tested in “sync” mode (with a --catalog argument)

Risks

The only downside of this change is that it breaks the current
config.json parameters for existing users.

@cmerrick
Copy link
Contributor

Hi @paulRbr, thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.

@cmerrick
Copy link
Contributor

You did it @paulRbr!

Thank you for signing the Singer Contribution License Agreement.

@paulRbr paulRbr force-pushed the use-google-api-client branch 2 times, most recently from 0e1c1cb to a836362 Compare November 20, 2020 19:37
These changes will make use of the official `google-api-python-client`
library instead of relying on manual HTTP requests.

Therer are two main advantages of these changes:

- the Tap doesn't need to worry about the Google API interaction
  details as its hidden away by the Google official lib.
- We can use the authentication helpers from the lib to ease the
  credentials management for the user. In that way the current PR
  implements two auth mean: installed OAuth client authentication or
  Service Accounts authentication.

The only downside of this change is that it breaks the current
`config.json` parameters for existing users.
@paulRbr
Copy link
Author

paulRbr commented Nov 20, 2020

Hi @kspeer825, hi @jeffhuth-bytecode what do you think of this change? Thanks!

@kspeer825
Copy link
Contributor

Hi @kspeer825, hi @jeffhuth-bytecode what do you think of this change? Thanks!

Hello, we have a backlog ticket to review this change. Thanks for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants