dab: add [databricks] config section to stack.toml for bundle generation #171
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Centralise all DAB generation parameters in stack.toml so the generator reads from one source.
Why
Currently databricks.yml hardcodes cluster specs, spark version, schedule, and target catalogs. These should live in stack.toml alongside the rest of the platform config, following the same pattern as [ci], [images], [mirrors].
Scope
Add to stack.toml:
Acceptance
cfg.databricks.bundle_namereturns"stack"cfg.databricks.targetsis iterable with dev/staging/prod