Configure cross-project dependencies

​

Steps

manifests:
  - name: jaffle_shop_platform # The producer project's name, from its dbt_project.yml
    type: paradime
    config:
      schedule_slug: running-raptor-a3f1b2 # The producer schedule's slug, not its display name
      api_key: ${PRODUCER_API_KEY}
      api_secret: ${PRODUCER_API_SECRET}
      api_endpoint: ${PRODUCER_API_ENDPOINT}

manifests:
  - name: jaffle_shop_platform # The producer project's name, from its dbt_project.yml
    type: paradime
    config:
      schedule_name: running-raptor-a3f1b2 # Despite the key's name, this is the schedule's slug
      api_key: ${PRODUCER_API_KEY}
      api_secret: ${PRODUCER_API_SECRET}
      api_endpoint: ${PRODUCER_API_ENDPOINT}

with monthly_revenue as (

    select * from {{ ref('jaffle_shop_platform', 'monthly_revenue') }}

),

...

​

Use an account API key

manifests:
  - name: jaffle_shop_platform
    type: paradime
    config:
      schedule_slug: running-raptor-a3f1b2
      api_secret: ${PRODUCER_API_TOKEN} # The account API key
      api_endpoint: ${PRODUCER_API_ENDPOINT}
      workspace_uid: ${PRODUCER_WORKSPACE_UID} # The producer workspace's UID

1. Go to Settings > API Keys, open the Company tab, and generate a key with only the Bolt schedules metadata viewer capability and access to only the producer workspace. You need to be an admin of the producer workspace.
2. Copy the API Token and API Endpoint. The success screen lists each workspace you selected with its UID: copy the producer workspace’s UID.
3. Set the three variables in the Default box of each consumer workspace, as in step 4.

​

Lineage across workspaces

​

Next steps

​

Troubleshooting

• Schedule for uuid ... could not be found in our system (dbt™ 1.10 to 1.12) or No schedule name '...' (dbt™ 1.7 to 1.9): there is no schedule with that slug in the workspace the key belongs to. Check that the config holds the schedule’s slug, not its display name, and that the key comes from the producer workspace. For an account API key, check workspace_uid.
• the following environment variable(s) referenced in the config are not set (dbt™ 1.11 and 1.12): add the named variables in the Default box of the consumer workspace.
• A Paradime API key, secret, and endpoint must be provided to dbt-loom (dbt™ 1.7 to 1.10): the variables your config names are missing in this environment. Set those names. You don’t need PARADIME_API_KEY, PARADIME_API_SECRET, or PARADIME_API_ENDPOINT.
• No valid api key was provided: the key or secret is wrong, expired, or revoked. Create a new key and update the variables.
• api key does not have capability: give the key the Bolt schedules metadata viewer capability.
• workspace_uid is required when authenticating with a company-level API token: add workspace_uid to the config.
• company API key is not authorised for workspace: give the account API key access to the producer workspace, or correct workspace_uid.
• No runs found for schedule, No latest run ID found for schedule, or No artifact found for schedule: the producer schedule has no recent run with a successful command that wrote target/manifest.json. Run the schedule, or point to one that runs dbt build, dbt run, or dbt compile. dbt™ 1.10 to 1.12 search the schedule’s 50 most recent runs. dbt™ 1.7 to 1.9 check only its latest run.
• No lineage for a consumer project in the Code IDE: the lineage view can show no lineage instead of the dbt-loom error. Check the build status in the Catalog tab, or run dbt parse in the terminal.