googledrive 1.0.0

The release of version 1.0.0 marks two events:

There is also new functionality that makes it less likely you’ll create multiple files with the same name, without actually meaning to.

Auth from gargle

googledrive’s auth functionality now comes from the gargle package, which provides R infrastructure to work with Google APIs, in general. The same transition is happening in several other packages, such as bigrquery and gmailr. This makes user interfaces more consistent and makes two new token flows available in googledrive:

Where to learn more:

Changes that a user will notice

OAuth2 tokens are now cached at the user level, by default, instead of in .httr-oauth in the current project. We recommend that you delete any vestigial .httr-oauth files lying around your googledrive projects and re-authorize googledrive, i.e. get a new token, stored in the new way.

googledrive uses a new OAuth “app”, owned by a verified Google Cloud Project entitled “Tidyverse API Packages”, which is the project name you will see on the OAuth consent screen. See our new Privacy Policy for details.

The local OAuth2 token key-value store now incorporates the associated Google user when indexing, which makes it easier to switch between Google identities.

The arguments and usage of drive_auth() have changed.

For full details see the resources listed in Where to learn more above. The change that probably affects the most code is the way to provide a service account token: - Previously: drive_auth(service_token = "/path/to/your/service-account-token.json") (v0.1.3 and earlier) - Now: drive_auth(path = "/path/to/your/service-account-token.json") (>= v1.0.0)

Auth configuration has also changed:

drive_has_token() is a new helper that simply reports whether a token is in place, without triggering the auth flow.

There are other small changes to the low-level developer-facing API:

overwrite = NA / TRUE / FALSE and drive_put()

Google Drive doesn’t impose a 1-to-1 relationship between files and filepaths, the way your local file system does. Therefore, when working via the Drive API (instead of in the browser), it’s fairly easy to create multiple Drive files with the same name or filepath, without actually meaning to. This is perfectly valid on Drive, which identifies file by ID, but can be confusing and undesirable for humans.

googledrive v1.0.0 offers some new ways to fight this:

Changes inspired by #230.

overwrite = NA / TRUE / FALSE

These functions gain an overwrite argument:

The default of overwrite = NA corresponds to the current behaviour, which is to “Just. Do. It.”, i.e. to not consider pre-existing files at all.

overwrite = TRUE requests to move a pre-existing file at the target filepath to the trash, prior to creating the new item. If 2 or more files are found, an error is thrown, because it’s not clear which one(s) to trash.

overwrite = FALSE means the new item will only be created if there is no pre-existing file at that filepath.

Existence checks based on filepath (or name) can be expensive. This is why the default is overwrite = NA, in addition to backwards compatibility.

drive_put()

Sometimes you have a file you will repeatedly send to Drive, i.e. the first time you run an analysis, you create the file and, when you re-run it, you update the file. Previously this was hard to express with googledrive.

drive_put() is useful here and refers to the HTTP verb PUT: create the thing if it doesn’t exist or, if it does, replace its contents. A good explanation of PUT is RESTful API Design — PUT vs PATCH).

In pseudo-code, here’s the basic idea of drive_put():

target_filepath <- <determined from arguments `path`, `name`, and `media`>
hits <- <get all Drive files at target_filepath>
if (no hits) {
 drive_upload(media, path, name, type, ..., verbose)
} else if (exactly 1 hit) {
 drive_update(hit, media, ..., verbose)
} else {
 ERROR
}

Other changes

All functions that support ... as a way to pass more parameters to the Drive API now have “tidy dots semantics”: !!! is supported for splicing and !! can be used on the LHS of :=. Full docs are in rlang::list2().

drive_find() now sorts by “recency”, by default.

drive_create() is a new function that creates a new empty file, with an optional file type specification (#258, @ianmcook). drive_mkdir() becomes a thin wrapper around drive_create(), with the file type hard-wired to “folder”.

In drive_mkdir(), the optional parent directory is now known as path instead of parent. This is more consistent with everything else in googledrive, which became very obvious when adding drive_create() and the general overwrite functionality.

drive_empty_trash() now exploits the correct endpoint (as opposed to deleting individual files) and is therefore much faster (#203).

Colaboratory notebooks now have some MIME type support, in terms of the type argument in various functions (https://colab.research.google.com/). The internal table of known MIME types includes "application/vnd.google.colab", which is associated with the file extension .ipynb and the human-oriented nickname "colab" (#207).

drive_endpoints() gains a singular friend, drive_endpoint() which returns exactly one endpoint. These helpers index into the internal list of Drive API endpoints with [ and [[, respectively.

Dependency changes

R 3.1 is no longer explicitly supported or tested. Our general practice is to support the current release (3.6), devel, and the 4 previous versions of R (3.5, 3.4, 3.3, 3.2). See Which versions of R do tidyverse packages support?.

gargle and magrittr are newly Imported.

rprojroot has been removed from Suggests, because we can now use a version of testthat recent enough to offer testthat::test_path().

googledrive 0.1.3

Minor patch release for compatibility with the imminent release of purrr 0.3.0.

googledrive 0.1.2

googledrive 0.1.1