Regenerate mlops_stacks snapshot from MLOps Stacks v0.5#164
Open
janniklasrose wants to merge 1 commit into
Open
Regenerate mlops_stacks snapshot from MLOps Stacks v0.5#164janniklasrose wants to merge 1 commit into
janniklasrose wants to merge 1 commit into
Conversation
Regenerate the mlops_stacks/ example from the upstream databricks/mlops-stacks template at tag v0.5 via `databricks bundle init`. The snapshot had not been refreshed since it was first added in 2023, so this pulls in three years of template evolution, including: - Repos -> Git folders and Workflows -> Lakeflow Jobs product renames (#225) - new quality monitoring pipeline (monitoring-resource.yml, MonitoredMetricViolationCheck.py) - notebooks relocated out of notebooks/ subdirs (Train.py, ModelValidation.py, etc.) - refreshed README code-structure section and CI/CD workflow files - databricks.yml gains the autogenerated uuid field and per-target catalog variables Generated bootstrap artifacts (cicd.tar.gz, cicd_params.json, project_params.json) are stripped to match the existing snapshot convention. `databricks bundle validate` passes on the dev target. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regenerates the
mlops_stacks/example from the upstream databricks/mlops-stacks template at tag v0.5 (released 2026-07-14) viadatabricks bundle init.Why
The
mlops_stacks/snapshot had not been refreshed since it was first added in 2023, so it had drifted three years behind upstream. Notably, it captures the product renames from mlops-stacks#225 (Repos → Git folders, Workflows → Lakeflow Jobs) at their upstream source, rather than hand-editing the generated snapshot. This is the follow-up to the revert in the product-renames PR, where those doc edits were backed out because this tree is generated upstream.What changed
Because this is a full v0.5 regen (not just the renames), it pulls in the accumulated template evolution:
monitoring-resource.yml,MonitoredMetricViolationCheck.py,metric_violation_check_query.pynotebooks/subdirs (Train.py,ModelValidation.py,BatchInference.py,ModelDeployment.py)deploy-cicd.yml,lint-cicd-workflow-files.yml)databricks.ymlgains the autogenerateduuidfield and per-targetcatalog_namevariablesNotes
cicd.tar.gz,cicd_params.json,project_params.json) are stripped to match the existing snapshot convention.databricks bundle validate -t devpasses (2 warnings are pre-existing template quirks: the intentional empty devhost:TODO placeholder and an upstreamdescriptionfield on the experiment resource).mlops_stacks/; based offmainrather than the product-renames branch.🤖 Generated with Claude Code