chore: copy databricks.yml.tmpl to pre-rendered app templates#407
Merged
Conversation
The generate-app-templates script now copies databricks.yml.tmpl from the source template into each generated app directory. This enables `databricks apps init --template <pre-rendered>` to render resource blocks, target variables, and project identity via --set values. The static databricks.yml remains as a readable reference; the CLI's copyTemplate() lexical walk order ensures the .tmpl version overwrites it in the output. Co-authored-by: Isaac
pkosiec
changed the title
MarioCadenas
approved these changes
Jun 2, 2026
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
2 participants
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.
Summary
Updates
tools/generate-app-templates.tsto copydatabricks.yml.tmplfrom the source template into each generated pre-rendered app directory.This enables
databricks apps init --template <pre-rendered>to render resource blocks, target variables, project name and workspace host via--setvalues — instead of keeping a staticdatabricks.ymlthat requires post-hoc YAML manipulation.How it works
databricks.ymlremains as a readable referencecopyTemplate()walks files in lexical order, sodatabricks.yml.tmplrenders second and overwrites the static file--setvalues flow through{{.bundle.resources}},{{.bundle.targetVariables}}, etc.Related PRs
This pull request and its description were written by Isaac.