dbt

type Granularity string

type Meta struct {
	// Warn, when set, receives advisories that are not build failures — passed
	// through to Render. nil means say nothing (#1114).
	Warn        func(string)
	DagID       string
	DagVersion  string
	Image       string
	Owner       string
	Description string
	Tags        []string
	Schedule    string
	Granularity Granularity
	// Connections and Variables are the secret names the dexaflow.yaml declares
	// (ADR 0045 / ADR 0055). They must reach the spec: what a task pod is allowed
	// to see is derived from what the DAG declares. Dropping them here does not
	// merely omit a field — under `auth.secret_scoping: enforce` the pod is
	// delivered nothing and the DAG fails inside the task rather than at compile
	// (#997). Under the default permissive scoping the pod still receives the
	// whole tenant vault, so the declarations are simply not honored; the
	// exception there is a secret that lives only in an external backend, which
	// is requested by declared name and so is never fetched at all. The dag.py
	// path emits both; this path built its spec from an explicit field list that
	// omitted them.
	Connections []string
	Variables   []string
	// Connection and Profile, when set, wrap each task's dbt command with the
	// runtime step that writes profiles.yml from the managed connection (ADR 0043).
	Connection string
	Profile    string
	// Schema overrides the dbt target schema in the generated profile.
	Schema string
	// ProjectDir scopes the dbt commands with --project-dir for a subdir project.
	ProjectDir string
	// ProfilesDir, when set, is passed as --profiles-dir. It is how a project
	// that ships its own profiles.yml gets honored: the base image points
	// DBT_PROFILES_DIR at an ephemeral /tmp dir so dbt's WRITES stay off the
	// read-only project (#852), and the side effect is that dbt never looks
	// inside the project at all (#994). Only reads happen through this — target
	// and log paths keep their own env and still land in /tmp. Ignored when a
	// managed connection is set: that path generates a profile into
	// DBT_PROFILES_DIR and must win over a checked-in file.
	ProfilesDir string
	// Local marks a Lite/host build: with no Connection, each task is prefixed with
	// the step that writes a default duckdb profiles.yml (the zero-config local
	// warehouse). Ignored on the Pro/image path. See Options.Local.
	Local bool
}

type Options struct {
	// Granularity selects the partition strategy; the empty value means node.
	Granularity Granularity
	// Warn, when set, receives advisories that are not build failures — today
	// only a folder group-key collision (#1114). This package is otherwise pure,
	// so the caller decides where a warning goes; nil means say nothing.
	Warn func(string)
	// Connection, when set, is a managed Dexaflow connection id; each task's dbt
	// command is prefixed with the runtime step that writes profiles.yml from it
	// (ADR 0043 #2), so no credential is baked into the image.
	Connection string
	// Profile is the dbt project's profile name (dbt_project.yml `profile:`), used
	// as the generated profiles.yml key. Meaningful only when Connection is set.
	Profile string
	// Schema, when set, overrides the dbt target schema in the generated profile
	// (otherwise the connection's or the "public" default is used).
	Schema string
	// ProjectDir scopes each command with --project-dir so dbt finds dbt_project.yml
	// when the project is a subdirectory of the DAG (#401). "." or empty adds nothing.
	ProjectDir string
	// ProfilesDir, when set, is passed as --profiles-dir. It is how a project that
	// ships its own profiles.yml gets honored: the base image points
	// DBT_PROFILES_DIR at an ephemeral /tmp dir so dbt's WRITES stay off the
	// read-only project (#852), and the side effect is that dbt never looks inside
	// the project at all (#994). Only reads go through this — DBT_TARGET_PATH and
	// DBT_LOG_PATH still carry the writes to /tmp. Ignored when Connection is set:
	// that path generates a profile into DBT_PROFILES_DIR and must win over a
	// file checked into the project.
	ProfilesDir string
	// Local marks a Lite/host build: with no Connection, each task is prefixed with a
	// step that writes a default duckdb profiles.yml — a zero-config local warehouse,
	// no server and no connection needed (L4). Ignored on the Pro/image path.
	Local bool
	// DagConnections are the connection ids declared at the top level of
	// dexaflow.yaml. They are stamped onto each task ALONGSIDE Connection, not
	// instead of it: declaredConnections (internal/storage) returns the task's
	// list whenever it is non-empty, so stamping only the managed connection
	// shadows the DAG's own declarations and they never reach the pod — a
	// pre-hook's connection silently missing under enforce scoping or an
	// external secrets backend.
	DagConnections []string
}