On this page
Kater CLI Build and check
kater ls
Lists the models and tests that a selection selects, one on each line, as dbt ls does.
Use it to check a selection before you give it to kater run, kater compile or kater test. It reads the declarations only, sends nothing to the warehouse and changes none of your files.
Examples
# Go to a workspace in your local copy of Kater contentcd connections/snowflake_prod_connection/workspaces/ad_reporting# List the query, its workspace root, the semantic model it reads and its datasetskater ls --select +query_contracts/spend_by_platform.sql# List the queries and charts that read the querykater ls --select query_contracts/spend_by_platform.sql+ --output name# List the tests of the shared ad_reporting modelkater ls --select semantic.ad_reporting --resource-type test# List what this branch changed since it left main, and what reads itkater ls --select state:modified+ --state git:mainOptions
It also takes the global options --json, --kater-root, --scope and --help.
What it prints
The nodes come in the order of their files. With --output selector, each line is a selection that names that node alone: its typed address, TYPE.NAME, such as query.spend_by_platform. When two nodes of one kind have the same name, as two workspaces in different connections can, the line also names the file, path:FILE,TYPE.NAME. You can give any line to --select as it is. name prints the node’s name, path its file, and json the node as one JSON line, with the keys of the manifest.