homelab/stack
1
0
Fork 0
Code Issues 127 Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

dab: add databricks.yml freshness check to CI via gen_config.py --check #177

New Issue
Closed
opened 2026-03-24 05:50:04 +00:00 by kert · 0 comments
kert commented 2026-03-24 05:50:04 +00:00
Owner
Copy Link

Goal

CI should fail if databricks.yml is stale.

Scope

  • Wire DAB generation into gen_config.py generate() so it emits databricks.yml
  • gen_config.py --check verifies databricks.yml matches generated output
  • CI already runs gen_config.py --check — no additional CI changes needed

Acceptance

  • gen_config.py --check fails if databricks.yml is stale
  • Adding a new pipeline without regenerating fails CI
## Goal CI should fail if databricks.yml is stale. ## Scope - Wire DAB generation into gen_config.py generate() so it emits databricks.yml - gen_config.py --check verifies databricks.yml matches generated output - CI already runs gen_config.py --check — no additional CI changes needed ## Acceptance - [ ] gen_config.py --check fails if databricks.yml is stale - [ ] Adding a new pipeline without regenerating fails CI
kert added this to the P22: DAB Generator — pluggable databricks.yml from pipeline registry milestone 2026-03-24 05:50:04 +00:00
kert added the cipipeline labels 2026-03-24 05:50:04 +00:00
kert closed this issue 2026-03-24 05:59:06 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label ci pipeline
Milestone
No items
No Milestone P22: DAB Generator — pluggable databricks.yml from pipeline registry
Projects
Clear projects
No project
Assignees
Clear assignees
dom kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#177
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?