Store init scripts in workspace files

Databricks recommends storing init scripts in workspace files in Databricks Runtime 11.3 LTS and above if you are not using Unity Catalog.

Note

There is limited support for init scripts in workspace files in Databricks Runtime 9.1 LTS and 10.4 LTS, but this support does not cover all common use patterns for init scripts, such as referencing other files from init scripts. Databricks recommends using init scripts in cloud object storage for Databricks Runtime 9.1 LTS and 10.4 LTS.

For more on workspace files, see What are workspace files?.

Where are init scripts stored in workspace files?

Init scripts can be stored in any location the user uploading the init script has proper permissions. See Folder permissions.

Like all workspace files, init scripts use access control lists (ACLs) to control permissions. By default, only the user uploading an init script and workspace admins have permissions on these files. See File permissions.

Note

Some ACLs are inherited from directories to all files within a directory.

Use init scripts stored in workspace files

Init scripts in workspace files are intended for use as cluster-scoped init scripts. See Use cluster-scoped init scripts.