Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not wait for app compute to start on bundle deploy #2144

Merged
merged 6 commits into from
Jan 28, 2025

Conversation

andrewnester
Copy link
Contributor

@andrewnester andrewnester commented Jan 14, 2025

Changes

This allows DABs to avoid waiting for the compute to start when app is initially created as part of "bundle deploy" which significantly improves deploy time.

Always set no_compute to true for apps

Tests

Covered by TestDeployBundleWithApp, currently fails until TF provider is upgraded to the version supporting no_compute option

Copy link
Contributor

@pietern pietern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change LGTM, but blocked on the TF bump.

github-merge-queue bot pushed a commit that referenced this pull request Jan 16, 2025
## Changes
When users create one or more Databricks apps in their bundle it can
lead to initial bundle deployment being slower because apps need to wait
until their compute is fully provisioned and started.

This PR adds a message to warn about it. This message will be removed
when `no_compute` option becomes available in TF provider and used in
DABs (#2144)
@andrewnester andrewnester changed the title Always set no_compute to true for apps Do not wait for app compute to start on bundle deploy Jan 28, 2025
@andrewnester andrewnester disabled auto-merge January 28, 2025 16:31
@andrewnester andrewnester added this pull request to the merge queue Jan 28, 2025
Merged via the queue into main with commit 413ca5c Jan 28, 2025
9 checks passed
@andrewnester andrewnester deleted the app-no-compute branch January 28, 2025 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants