CLI and Terraform

Install the CLI and authenticate:

npm install --global @embrasure/cli
embrasure auth login
embrasure doctor

Task	Command
List connectors	`embrasure connectors list`
Inspect impact	`embrasure lineage impact <relation_ref> --connector <id>`
Export lineage	`embrasure lineage export --out lineage.ndjson`
List Scouts	`embrasure monitor scouts list`
Run a Scout	`embrasure monitor scouts run <id> --yes`
Inspect schema changes	`embrasure schema changes list`
Investigate a table	`embrasure investigate table <relation_ref>`

For CI, store EMBRASURE_API_TOKEN in the CI secret manager and select a workspace through config or --workspace.

Terraform provider

Configure the provider with api_url and a token supplied through EMBRASURE_API_TOKEN:

terraform {
  required_providers {
    embrasure = {
      source = "embrasure/embrasure"
    }
  }
}

provider "embrasure" {
  workspace_id = var.embrasure_workspace_id
}

The provider manages:

embrasure_connector
embrasure_lineage_source
embrasure_scout
embrasure_alert_destination

Imports use the stable resource ID. Plans redact secrets, and updates preserve provider identity so a configuration change cannot silently rebind lineage evidence.

Terraform provider

On this page