skypilot
1# Example showcasing how env vars can be used in the file_mounts section.
2
3# You can set the default values for env vars in this 'envs' section.
4# When launching, `sky launch --env ENV=val` will override the default.
5envs:
6MY_BUCKET: skypilot-temp-gcs-test
7MY_LOCAL_PATH: tmp-workdir
8MODEL_SIZE: 13b
9
10resources:
11cloud: gcp
12
13# You can use env vars in
14# - the destination: source paths
15# - for bucket mounting
16# - the "name" (bucket name) and "source" (local dir/file to upload) fields.
17#
18# Both syntaxes work: ${MY_BUCKET} and $MY_BUCKET.
19file_mounts:
20/mydir:
21name: ${MY_BUCKET} # Name of the bucket.
22store: gcs
23mode: MOUNT
24
25/mydir2:
26name: $MY_BUCKET # Name of the bucket.
27store: gcs
28mode: MOUNT
29
30/another-dir:
31name: ${MY_BUCKET}-2
32source: ["~/${MY_LOCAL_PATH}"]
33store: gcs
34mode: MOUNT
35
36/another-dir2:
37name: $MY_BUCKET-2
38source: ["~/${MY_LOCAL_PATH}"]
39store: gcs
40mode: MOUNT
41
42/checkpoint/${MODEL_SIZE}: ~/${MY_LOCAL_PATH}
43
44run: |
45echo Env var MY_BUCKET has value: ${MY_BUCKET}
46echo Env var MY_LOCAL_PATH has value: ${MY_LOCAL_PATH}
47
48ls -lthr /mydir
49ls -lthr /mydir2
50ls -lthr /another-dir
51ls -lthr /another-dir2
52ls -lthr /checkpoint/${MODEL_SIZE}
53