A connection is a source a project declares once: an SMB share, a bucket, a SharePoint library, a database. The platform keeps its credentials and reads on your behalf, so they never reach your code. Two ways to use one:
  • a sync copies what the connection holds into a dataset or a mediaset, on demand or on a schedule;
  • a transform declares the connection as an input and reads it itself, picking the files it wants.

List and get

Files

Listings are recursive and paged. Each entry carries path (relative to the connection’s root), filename, size, last_modified and is_dir.
glob follows the same rule as a sync’s path_glob: * stays within a directory, ** descends.

Download

In a transform

Bind the connection with Connection("<project>.<slug>"). The function receives a read-only filesystem over the same relay:
The lineage shows the connection feeding the output. To process only new files on each run, see Incremental transforms.
Connections are read-only from code: a connection is where data comes from, and a transform writes into its output dataset.