Uh oh!
There was an error while loading. Please reload this page.
Add support for configuring app.yaml options for apps via bundle config - #4271
Merged
Conversation
andrewnester
requested review from
anton-107, denik, pietern and shreyas-goenka
as code ownersJanuary 13, 2026 11:13
andrewnestertemporarily deployed
to
test-trigger-is
January 13, 2026 11:14 — with 
GitHub Actions
Inactive
andrewnestertemporarily deployed
to
test-trigger-is
January 13, 2026 11:26 — with GitHub Actions
Inactive
andrewnestertemporarily deployed
to
test-trigger-is
January 13, 2026 11:41 — with GitHub Actions
Inactive
Collaborator
Commit: 17f9fb5
30 interesting tests: 15 RECOVERED, 10 KNOWN, 4 flaky, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
andrewnestertemporarily deployed
to
test-trigger-is
January 13, 2026 12:38 — with GitHub Actions
Inactive
denik
reviewed
Jan 13, 2026
Uh oh!
There was an error while loading. Please reload this page.
| @@ -0,0 +1,6 @@ | |||
| Local = false | |||
Contributor
There was a problem hiding this comment.
Can we have it on testserver as well? Cloud-only tests are painful to update.
ContributorAuthor
There was a problem hiding this comment.
This would be a relatively useless test, as here we are confirming backend behaviour that it overwrites values in app.yaml with whatever is passed to the Deploy call
Contributor
There was a problem hiding this comment.
I see. However, even if test itself is not useful, having local run means we can regenerate the output quickly with 'make test-update'.
The longer running 'make test-update-aws' skips tests that have Local=true.
Ideally, we are able to update all test output with local runs.
andrewnestertemporarily deployed
to
test-trigger-is
January 13, 2026 13:38 — with GitHub Actions
Inactive
andrewnestertemporarily deployed
to
test-trigger-is
January 13, 2026 13:40 — with GitHub Actions
Inactive
eng-dev-ecosystem-bot
commented
Jan 14, 2026
Collaborator
Commit: c75194b
33 interesting tests: 17 RECOVERED, 9 flaky, 6 KNOWN, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-taggingBot
added a commit
that referenced
this pull request
Jan 14, 2026
## Release v0.283.0 ### Notable Changes * Bundle commands now cache the user's account details to improve command latency. To disable this, set the environment variable DATABRICKS_CACHE_ENABLED to false. ### CLI * Add commands to pipelines command group ([#4275](#4275)) ### Bundles * Add support for configuring app.yaml options for apps via bundle config ([#4271](#4271)) * Enable caching user identity by default ([#4202](#4202)) * Do not show single node warning when is_single_node option is explicitly set ([#4272](#4272)) * Fix false positive folder permission warnings and make them more actionable ([#4216](#4216)) * Pass additional Azure DevOps system variables ([#4236](#4236)) * Replace Black formatter with Ruff in Python bundle templates for faster, all-in-one linting and formatting ([#4196](#4196)) * engine/direct: support quality monitors ([#4278](#4278)) * Improve folder permissions warning ([#4216](#4216)) ### Dependency updates * Upgrade TF provider to 1.102.0 ([#4235](#4235)) * Upgrade Go SDK to 0.96.0 ([#4206](#4206))
denik pushed a commit
that referenced
this pull request
May 20, 2026
…ig (#4271) ## Changes Add support for configuring app.yaml options for apps via bundle config This change uses new fields from Apps.Deploy call: `Command` and `EnvVars`. ## Why This change allows users to configure their Databricks Apps differently for different targets Fixes#3679 ## Tests Added an acceptance test <!-- If your PR needs to be included in the release notes for next release, add a separate entry in NEXT_CHANGELOG.md as part of your PR. -->
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Release v0.283.0 ### Notable Changes * Bundle commands now cache the user's account details to improve command latency. To disable this, set the environment variable DATABRICKS_CACHE_ENABLED to false. ### CLI * Add commands to pipelines command group ([#4275](#4275)) ### Bundles * Add support for configuring app.yaml options for apps via bundle config ([#4271](#4271)) * Enable caching user identity by default ([#4202](#4202)) * Do not show single node warning when is_single_node option is explicitly set ([#4272](#4272)) * Fix false positive folder permission warnings and make them more actionable ([#4216](#4216)) * Pass additional Azure DevOps system variables ([#4236](#4236)) * Replace Black formatter with Ruff in Python bundle templates for faster, all-in-one linting and formatting ([#4196](#4196)) * engine/direct: support quality monitors ([#4278](#4278)) * Improve folder permissions warning ([#4216](#4216)) ### Dependency updates * Upgrade TF provider to 1.102.0 ([#4235](#4235)) * Upgrade Go SDK to 0.96.0 ([#4206](#4206))
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Changes
Add support for configuring app.yaml options for apps via bundle config
This change uses new fields from Apps.Deploy call:
CommandandEnvVars.Why
This change allows users to configure their Databricks Apps differently for different targets
Fixes#3679
Tests
Added an acceptance test