[Feature Request] - Rclone - Scope - Drive appdata

[GGRm0]

There is a need to mount Google Drive with limited access "https://www.googleapis.com/auth/drive.appdata " Is the implementation of the function planned? The RClone documentation mentions such functionality. https://rclone.org/drive/

Kasm Volume Config Example:

{
     "driver" : "rclone",
     "driver_opts" : {
         "type" : "drive.appfolder",
         "uid" : "1000",
         "gid" : "1000",
         "allow_other" : "true"
      }
}

Existing Resources

• [x] Please search the existing issues for related items
• [x] Consult the product documentation : Docs
• [x] Consult the FAQ : FAQ
• [x] Consult the Troubleshooting Guide : Guide
• [x] Reviewed existing training videos: Youtube

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

[j-travis]

Here is an example of using the drive.file permission which is similar. You may be able to adapt this to drive.appfolder

Modify the Scopes at step 8 (https://kasmweb.com/docs/latest/guide/storage_providers/gdrive.html#id3) to https://www.googleapis.com/auth/drive.file instead of https://www.googleapis.com/auth/drive .

Then when configuring the Storage Mapping in workspaces (https://kasmweb.com/docs/latest/guide/storage_providers/gdrive.html#kasm-storage-provider-config) use that same https://www.googleapis.com/auth/drive.file scope

If the end user has previously registered their cloud storage mapping in Kasm prior to changing the scopes, they will have to delete app connections from their account https://myaccount.google.com/connections?filters=3,4&hl=en , delete the cloud mapping from Kasm, then re-created it.

You may be able to do something similar with the drive.appfolder scope but you'd have to try