🤔 Problem

Two use-cases

There are lots of benefits to this improvement, but two primary drivers are:

Support other user-friendly commercial storage

People like using the data connectors, but their data is often in places that require OAuth, e.g. Google Drive. This would make it much simpler for them to have their own storage that they are used to.

Support data repositories like dCache

The large astronomy projects that host data at CSCS use dCache as one of the storage solutions. It offers WebDAV access via OAuth. Enabling this storage would really open up Renku as a viable tool for big international collaborations like SKAO and CTAO.

🍴 Appetite

6 weeks

🎯 Solution

Connected services should include storage providers like Google Drive, OneDrive. The flow to connect these is exactly the same as for the existing services already offered on the “integrations” page.

We should also use the mechanism that was recently implemented which informs the user of a missing integration if they try to launch a session without connecting the service.

Creating an OAuth DC

• name
• path within the storage
• token:
  • use my connected service
    • → activate
  • OR enter token OR username and password

Flow

• Create data connector