[
https://issues.apache.org/jira/browse/ARROW-16880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569676#comment-17569676
]
Will Jones commented on ARROW-16880:
------------------------------------
I looked into this a bit, and someone should correct me I'm off base, but I'm
not sure integration will be useful except in very specific cases. gargle
basically let's you have an OAuth flow in R, where it can request specific
scopes. When I tried this with the default app ID, Google came back to me
saying it blocked access. So I think in order to use it you need to create your
own OAuth app in Google, and hook it up to gargle.
It seems the likely auth flows for our users are:
1. For analysts in local environments: Use application default credentials
(run {{{}gcloud auth application-default login{}}}) and everything will run
fine.
2. For deployed apps (e.g. Shiny): create a service account, download a
credentials file onto the server, and provide the path to the downloaded
credentials file to {{GcsFileSystem$create()}}
I'm still trying to grok GCP's authentication approach, so I welcome any input.
> [R] Test GCS auth with gargle/googleAuthR
> -----------------------------------------
>
> Key: ARROW-16880
> URL: https://issues.apache.org/jira/browse/ARROW-16880
> Project: Apache Arrow
> Issue Type: New Feature
> Components: R
> Reporter: Neal Richardson
> Assignee: Will Jones
> Priority: Major
> Fix For: 9.0.0
>
>
> These are the main packages that let folks worth with Google Cloud from R, so
> we should make sure we can play nicely with their auth methods, how they
> cache credentials, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
