-
Notifications
You must be signed in to change notification settings - Fork 428
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
migrate from drive/v2 to drive/v3 #650
Comments
Hello, reading that migration guide in the documentation i found that it says that the v3 allowFileDiscovery Permission is equal to the v2 withLink Permission: allowFileDiscovery=false : withLink=true It is then explained in v2 documentation (but the description is not self explaining): So setting withLink=true in v2 will turn that "Anyone with the link" function on (aka indexing file off) Hoping this can help adding this function in v2 and let the migration process simple |
Ahh I see. Thank you @thebaddie. I'll take a look at it over the weekend, or feel free to add it in. |
Hi @odeke-em any news about allowFileDiscovery/withLink? |
Hello there @thebaddie. Oops, my apologies, I totally forgot about this :) Let me take a look at it now before bed. Hope you'll be able to test it too? |
Enables sharing to anyone with the link but the file won't be publicly indexed as is usually with files that are published publicly. ```shell $ drive share --with-link ComedyPunchlineDrumSound.mp3 ``` Fixes #568. Follows suggestions in #650 (comment).
We need to migrate drive from v2 to v3. v3 has some fields like
allowFileDiscovery
, that explicitly turns off indexing of a file. This issue #568 (comment) and comment #648 (comment) are the motivation for the migration, plus also we don't want to be left behind.For more on v3, please see https://developers.google.com/drive/v3/web/migration#parameters.
The text was updated successfully, but these errors were encountered: