The RUN_ID variable contains a cryptographically secure ID associated with each run of your project. This is automatically generated when you use prism run or prism spark-submit.
The SLUG variable contains a slug for each run of your project. Note that the SLUG is not cryptographically secure, but it much more human-readable than RUN_ID. It is automatically generated when you use prism run or prism spark-submit.
Your run's SLUG is displayed in the logs when you run your project:
$ cd my_first_project
$ prism run
--------------------------------------------------------------------------------
<HH:MM:SS> | INFO | Running with prism v0.1.9rc2...
<HH:MM:SS> | INFO | Found project directory at /Users/mihirtrivedi/Desktop/bom
<HH:MM:SS> | INFO | RUNNING parsing prism_project.py................................................ [RUN]
<HH:MM:SS> | INFO | FINISHED parsing prism_project.py............................................... [DONE in 0.03s]
<HH:MM:SS> | INFO | RUNNING module DAG.............................................................. [RUN]
<HH:MM:SS> | INFO | FINISHED module DAG............................................................. [DONE in 0.01s]
<HH:MM:SS> | INFO | RUNNING creating pipeline, DAG executor......................................... [RUN]
<HH:MM:SS> | INFO | FINISHED creating pipeline, DAG executor........................................ [DONE in 0.01s]
<HH:MM:SS> | INFO | ===================== tasks (vermilion-hornet-Gyycw4kRWG) =====================
<HH:MM:SS> | INFO | 1 of 1 RUNNING module01.py...................................................... [RUN]
<HH:MM:SS> | INFO | 1 of 1 FINISHED module01.py..................................................... [DONE in 0.01s]
<HH:MM:SS> | INFO | Done!
--------------------------------------------------------------------------------
In the above example, vermilion-hornet-Gyycw4kRWG is your run's SLUG.
Important: if your prism_project.py file does not have a RUN_ID or SLUG, then Prism will throw an error. Make sure these are defined.
