Prism
v0.1.9rc2
v0.1.9rc2
  • 👋Welcome to Prism!
  • Getting Started
    • Installation
    • Creating your first project
    • Why Prism?
  • Fundamentals
    • Tasks
      • tasks
      • hooks
        • hooks.sql
        • hooks.spark
        • hooks.dbt_ref
    • Targets
      • Multiple targets
    • Config files
      • prism_project.py
        • RUN_ID / SLUG
        • SYS_PATH_CONF
        • THREADS
        • PROFILE_YML_PATH / PROFILE
        • PRISM_LOGGER
        • TRIGGERS_YML_PATH / TRIGGERS
      • Profile YML
      • Triggers YML
    • Jinja
      • __file__ and Path
      • prism_project
      • wkdir
      • parent_dir
      • concat
      • env
  • Adapters
    • Overview
    • sql
      • BigQuery
      • Postgres
      • Redshift
      • Snowflake
      • Trino
    • PySpark
    • dbt
  • Agents
    • Overview
    • Docker
    • EC2
  • CLI
    • Command Line Interface
    • init
    • compile
    • connect
    • create
      • agent
      • task
      • trigger
    • graph
    • run
    • spark-submit
    • agent
      • apply
      • run
      • build
      • delete
  • Advanced features
    • Concurrency
    • Logging
    • Triggers
    • Retries
    • Python Client
  • API Reference
    • prism.task.PrismTask
    • @task(...)
    • @target(...)
    • @target_iterator(...)
    • tasks.ref(...)
    • hooks.sql(...)
    • hooks.dbt_ref(...)
  • Use Cases
    • Analytics on top of dbt
    • Machine Learning
  • Wiki
    • DAGs
Powered by GitBook
On this page
  • Usage
  • Example
  • Required arguments
  • Optional arguments
  1. CLI
  2. create

trigger

Usage

prism create trigger is used to create and update the triggers YML configuration file.

Usage: prism create trigger [-h] --type TYPE [--full-tb] [-l]

Create a triggers YML file at the TRIGGERS_YML_PATH in `prism_project.py`.

Options:
  -h, --help         show this help message and exit

Subcommand Options:
  --type TYPE        Trigger type. As of now, only acceptable value is `function`

General Options:
  --full-tb          Display the full traceback for errors in the project; default is False
  -l, --log-level    Log level, must be one of `info`, `warn`, `error`, or `debug`. Default is `info`

Here's what prism create trigger does under the hood:

  1. Parses the prism_project.py file and gets the TRIGGERS_YML_PATH value. If this value isn't specified, then it defaults to the project directory.

  2. It checks to see if TRIGGERS_YML_PATH exists

    • If it doesn't, it creates a file at TRIGGERS_YML_PATH and populates it with a trigger of type --type

    • If it does, it then adds a profile of type --type to the existing file

Example

Here's what the output will look like in Terminal (if there are no errors in the project):

$ prism create trigger --type function
--------------------------------------------------------------------------------
<HH:MM:SS> | INFO  | Running with prism v0.1.9rc2...
<HH:MM:SS> | INFO  | Found project directory at /Users/my_first_project
 
<HH:MM:SS> | INFO  | RUNNING EVENT 'parsing prism_project.py'................................................ [RUN]
<HH:MM:SS> | INFO  | FINISHED EVENT 'parsing prism_project.py'............................................... [DONE in 0.03s]
 
<HH:MM:SS> | INFO  | Setting up triggers...
 
<HH:MM:SS> | INFO  | Done!
--------------------------------------------------------------------------------
$ 

Here's what the triggers.yml file looks like after running the above command:

# triggers.yml

triggers:
  <trigger name here>:
    type: function
    function: <import path to function>  # make sure your project has access to this import path via SYS_PATH_CONF!
    kwargs:  # this is optional!
      arg1: value1

Required arguments

Here are the required arguments you must specify with trigger:

  • --type : Trigger type. As of now, only type function is supported.

Optional arguments

Here are the optional arguments you can run with trigger:

  • --full-tb : Display full traceback if errors arise at any stage of the pipeline

  • --log-level: Log level, one of info, warn, error, or critical.

  • --vars: Prism variables as key-value pairs key=value. These overwrite any variable definitions in prism_project.py. All values are read as strings.

  • --context : Prism variables as JSON. Cannot co-exist with --vars. These overwrite any variable definitions in prism_project.py.

PrevioustaskNextgraph

Last updated 1 year ago