...
Do not use the Manager Files feature as a file system or storage. Use a Cloud storage provider to store production data. File Assets should not be used as a file source or as a destination in production pipelines. When you configure File Reader and Writer Snaps, set the file path to a cloud provider or external file system.
| Info |
|---|
Supported use cases for reading from and writing to
Pipelines can reference these types of files when processing data. Otherwise, do not use |
During Pipeline development, you can use Manager > Files to store static JAR files, expression library files, JDBC drivers, and parameter files for SnapLogic to use during Pipeline development. For example, you might upload .xls, .txt, .json or .csv files to design a Pipeline that executes on files stored in an S3 bucket during production.
The maximum file size is 100MB. You can upload them using Snaps that support file upload or in SnapLogic Manager, as described on this page. To reference an uploaded file in a Pipeline's field, use the following convention: sldb:///<YOUR_FILE_PATH>.
Limitations
File Assets are intended only for specialized files that a Pipeline uses to reference certain data, such as accounts, expressions, or JAR files. Because the platform does not restrict how files are used, admins should audit File uploads in their Orgs through the Activity Log.
File Assets have the following limitations:
The maximum file size is 100MB.
Projects should not contain more than 100,000 total Assets. File Assets count towards that total.
The following table lists files types that are not supported and describes why:
HTML-associated files can contain cookie-stealing JavaScript and web bugs: | PHP scripts might execute arbitrary code on the server: | Other types that might be interpreted by some servers: | Window executable files that can cause harm: |
|---|---|---|---|
|
|
|
|
...