nadment opened a new issue, #9531: URL: https://github.com/apache/hop/issues/9531
### What would you like to happen? Read and write Excel files directly from and to SharePoint: no manual download, no synced OneDrive folder, no intermediate copy. Point the Microsoft Excel input or Microsoft Excel writer transform at a path such as `sharepoint:///Finance/Documents/reports/budget.xlsx` and the pipeline works on the file where the business users keep it, including the files of a Microsoft Teams channel. Add a new VFS plugin that exposes Microsoft SharePoint Online document libraries as a named VFS file system, through the Microsoft Graph API. A lot of business data lives in SharePoint and Teams as Excel or CSV files. Today Hop has no way to reach them: users have to download the files by hand, sync them to a local drive, or script the transfer outside of Hop. With this plugin, a SharePoint file is just another VFS path, so it works with every transform and action that accepts a VFS location (Excel input and writer, Text file input and output, Copy files, Get file names, etc.) and in the VFS File Explorer. **Path** ``` <connection name>:///<site>/<library>/<folder>/<file> ``` | Path | What it is | |---|---| | `sharepoint:///` | The SharePoint sites of the tenant | | `sharepoint:///Finance` | The document libraries of the site `Finance` | | `sharepoint:///Finance/Documents` | The root folder of the library `Documents` | | `sharepoint:///Finance/Documents/reports/budget.xlsx` | A file in that library | The files of a Microsoft Teams channel are reached the same way, since a channel is a folder in the SharePoint site of its team: `sharepoint:///<team>/Documents/<channel>/<file>`. **New metadata type: SharePoint Connection** The name of the connection is the scheme of the path, and the credentials are stored in the connection, never in the path. The connection signs in as a Microsoft Entra ID application with one of: * a client secret * a client certificate (PEM) * a managed identity / the default Azure credential chain The editor has a Test button and a button to explore the connection in the VFS File Explorer. **Supported operations** * Browse sites, document libraries, folders and files * Read files * Create and replace files (large files are sent through an upload session) * Create folders, delete, rename and move files and folders inside a document library **Permissions** Microsoft Graph application permissions, with admin consent: * `Sites.Read.All` to read * `Sites.ReadWrite.All` to also write * `Sites.Selected` to restrict the application to the sites it was granted. These sites can not be listed, but they are reachable by their path. **Known limitations** * Sites and document libraries can be listed but not created, renamed or deleted. * Appending to a file is not supported. * Moving a file to another library or site is a copy followed by a delete. * A file is buffered in a local temporary file while it is written and is sent when it is closed. * OneDrive personal drives are not covered, this could be a follow-up. **Documentation** Two new pages in the user manual: the SharePoint VFS page and the SharePoint Connection metadata type page. I have a working implementation (`plugins/tech/microsoft365`) and will submit a pull request. ### Issue Priority Priority: 3 ### Issue Component Component: VFS, Component: Metadata -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
