How to Set the Application Datasource Name

Goal

Change the Veza datasource name that OAA-runner uses when pushing data, so that the data appears under a specific name in Veza instead of the auto-generated default. This should only be used in rare cases when a single data source is not adequate.

When to use this

By default, OAA-runner generates a datasource name from the application name: "{app.name} Datasource". Set app.datasource when you need a specific name — for example, to match an existing datasource in Veza, to use a shorter or cleaner label, or to make the name consistent across multiple runs with different app name configurations.

Prerequisites

  • A config.yaml with an app block.

Steps

1. Add datasource: to the app block

app:
  name: My App
  datasource: my-custom-datasource

That’s it. All sources that don’t set their own datasource: will push to my-custom-datasource.

2. Verify

Run with --dry-run to confirm the datasource name without pushing to Veza:

cd src && uv tool run --from oaa-runner oaa app \
  --config-file path/to/config.yaml \
  --dry-run

Datasource resolution order

OAA-runner resolves the datasource for each source in this order:

Priority

Where set

Example

1 (highest)

datasource: on the source

sources.users.datasource: users-ds

2

datasource: on the app

app.datasource: my-custom-datasource

3 (default)

Auto-generated

"{app.name} Datasource"

app.datasource acts as a fallback for all sources. A source-level datasource: always wins over it. See how-to-use-multiple-datasources.md for the source-level override pattern.