-
Notifications
You must be signed in to change notification settings - Fork 67
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
Add support for file revisions #193
Labels
Comments
Awesome @Foggy2 ! Checking it out! |
Hey @Foggy2 - I'm still working on this, hoping to have it built out by the weekend. Just wanted to provide an update since this issue hadn't been responded to in a while! |
scrthq
added a commit
that referenced
this issue
Jul 17, 2019
## 2.30.0 * [Issue #193](#193) * Added: Drive Revision functions: * Get-GSDriveRevision * Remove-GSDriveRevision * Update-GSDriveRevision * [Issue #210](#210) * Fixed: Update-GSUser was not accepting User ID's as the User parameter * [Issue #209](#209) * Added: Support for inline image downloading with Get-GSGmailMessage where the image is not included on the Attachments property of the parsed message object. * Fixed: Get-GSGmailMessage will now automatically set the Format to Raw if either ParseMessage or SaveAttachmentsTo is passed, as ParseMessage is a requirement in order to be able to access the message attachments as needed. * [Issue #204](#204) * Added: Recurse parameter to Get-GSDriveFileList to allow recursively listing all files and subfolders underneath the result set. Confirmed setting the Limit parameter also works as expected with Recurse included, stopping is the original limit is reached. * Added: Get-GSDriveFolderSize function to return the calculated total size of the files in the specified folder(s). * Miscellaneous * Added: Rfc822MsgId parameter to Get-GSGmailMessageList to easily build a query looking for a specific RFS 822 Message ID. * Added: Pipeline support for *-GSDrivePermission functions to enable piping Drive Files into them to manage permissions without looping manually.
scrthq
added a commit
that referenced
this issue
Jul 17, 2019
## 2.30.0 * [Issue #193](#193) * Added: Drive Revision functions: * `Get-GSDriveRevision` * `Remove-GSDriveRevision` * `Update-GSDriveRevision` * [Issue #210](#210) * Fixed: `Update-GSUser` was not accepting User ID's as the User parameter * [Issue #209](#209) * Added: Support for inline image downloading with `Get-GSGmailMessage` where the image is not included on the Attachments property of the parsed message object. * Fixed: `Get-GSGmailMessage` will now automatically set the `Format` to `Raw` if either `ParseMessage` or `SaveAttachmentsTo` is passed, as `ParseMessage` is a requirement in order to be able to access the message attachments as needed. * [Issue #204](#204) * Added: `Recurse` parameter to `Get-GSDriveFileList` to allow recursively listing all files and subfolders underneath the result set. Confirmed setting the `Limit` parameter also works as expected with `Recurse` included, stopping is the original limit is reached. * Added: `Get-GSDriveFolderSize` function to return the calculated total size of the files in the specified folder(s). * Miscellaneous * Added: `Rfc822MsgId` parameter to `Get-GSGmailMessageList` to easily build a query looking for a specific RFS 822 Message ID. * Added: Pipeline support for `*-GSDrivePermission` functions to enable piping Drive Files into them to manage permissions without looping manually.
deployed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @scrthq
I have come across the situation a couple times where it would be handy for us to be able to programmatically download the file revisions for specific files from drive.
The API seems to indicate that it should be quite straight forward.
https://developers.google.com/drive/api/v2/reference/revisions
I am thinking that we would need a new function to retrieve all of the revisions and then perhaps a new parameter on the
Get-GSDriveFile
function that accepts the revision ID.Thanks!
The text was updated successfully, but these errors were encountered: