-
Notifications
You must be signed in to change notification settings - Fork 6
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
Private key filename #44
base: main
Are you sure you want to change the base?
Conversation
Well, the windows errors look like they are coming from DuckDB's httplib that I added to the includes somehow. Odd. I'm not sure where to go next on that, but I can look next week. |
i think this probably means you have the httplib on your machine but not in CI |
might be a modification to CMakeLists but i'm not expert |
Love the functionality in this PR Some general thoughts:
|
-- (see "Getting a Google API Access Private Key" below) | ||
CREATE SECRET ( | ||
TYPE gsheet, | ||
PROVIDER private_key, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think google would normally refer to this as key_file
Actually, it looks like we might be able to avoid OAuth all together if we are using a service account: https://developers.google.com/identity/protocols/oauth2/service-account#jwt-auth This seems like it might be much simpler.
|
This allows you to refer directly to the JSON file that Google outputs instead of having to pass in a key as a string.
One consequence is that the key itself is not persisted within the secret, just the filename. I leave fixing that for another PR!
And, this time, I tested with a debug build so it should actually build and run on other people's machines... In theory!!
Closes #42.