Skip to main content

How to Bundle Data Sources into a Data Drive

Attach the same combination of data sources to multiple runs without rebuilding the configuration each time.

A run mounts one data source. When an application needs two, or needs the same pair of sources on every run, put them in a Data Drive. The drive is itself mountable, and each source inside it lands at its own sub-path.

Create the drive​

Click New Data Drive in the Data Drives section of the Data and Sensors page. Give the drive a name, unique across your account, then add one mount point per data source you want in it. A drive holds any number of them.

Figure 1 builds the example used through the rest of this guide. The drive is named myNewDrive and holds the Signaloid Cloud Storage at mountStorage and an AWS S3 bucket at mountAWSBucket. Both locations are relative to where the drive itself ends up mounted, not to the root of the run.

Figure 1. Creating a Data Drive on your Signaloid Cloud Developer Platform account, with the Signaloid Cloud Storage mounted at mountStorage and an AWS S3 bucket mounted at mountAWSBucket.

Mount the Drive on a run​

The drive appears in the Mount Data Source () picker alongside individual sources, in the Code Playground and on connected repositories alike. Mount it once and every source inside it comes with it.

Figure 2 mounts myNewDrive at myNewDriveMount in the Code Playground. The application then reads the Signaloid Cloud Storage at myNewDriveMount/mountStorage and the S3 bucket at myNewDriveMount/mountAWSBucket:

FILE *  storage = fopen("myNewDriveMount/mountStorage/input.csv", "r");
FILE *  bucket  = fopen("myNewDriveMount/mountAWSBucket/output.csv", "w");
Figure 2. Adding the new Data Drive as a source in the Code Playground and mounting it at myNewDriveMount.

Change or remove the Drive​

Edit Configuration on the drive card reopens the dialog with the current name and mount points populated, so you can rename the drive, add a mount point, or remove one.

Disconnect () removes the drive after a confirmation. The data sources inside it are left untouched, and stay available on their own.

Remove a source from every drive that mounts it before disconnecting the source itself. The platform blocks the disconnect until you do. See How to Connect an AWS S3 Bucket.

See Data Drives for the drive card and dialog reference.

Last updated on