Subsequent cluster deployments always causes updates on TF if cluster has DATA_SECURITY_MODE: SINGLE_USER
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, terraform
- Domain
- cli, infrastructure
Research direction
Read acceptance/bundle/integration_whl/interactive_single_user and compare its direct deployment behavior with the Terraform behavior described in the issue and PR 3768. Done when acceptance coverage records the intended handling of subsequent deployments for DATA_SECURITY_MODE: SINGLE_USER and the regression behavior is resolved.
Written by the indexing model from the issue text.
Description
Describe the issue
Direct deployment does not update/restart the cluster on subsequent deploys which is correct, and thus changes for the wheel are not picked, which is expected in such case.
But this is a regression behaviour comparing to TF because TF test behaviour for wheel jobs on single-user interactive clusters is technically incorrect because TF in such a setup produces permanent drift (incorrect), which leads to cluster restart on each bundle deploy, and therefore wheel changes are picked up
# databricks_cluster.shared_autoscaling will be updated in-place
~ resource "databricks_cluster" "shared_autoscaling" {
id = "1015-102652-xxxxxxx"
- single_user_name = "aaaaaaaabbbb-bbbb-cccc-dddd-bb6ce382668a" -> null
# (19 unchanged attributes hidden)
# (1 unchanged block hidden)
}
More details here https://github.com/databricks/cli/pull/3768
Configuration
See acceptance/bundle/integration_whl/interactive_single_user acceptanct test
Is this a regression?
Yes, comparing to TF deployment behaviour
- Dominant language
- Go
- Stars
- 427
- Forks
- 267
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 233
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databricks/cli
-
Apps commands only accept relative path to app.ymlPossibly taken @yuri-rod claimed this 38 days ago. OpenCLI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
databricks/cli#6910 ·
Maintainers usually reply within 1 day
-
DABs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
databricks/cli#6670 · 1 reaction ·
Maintainers usually reply within 1 day
-
Bump vulnerable dependencies workflow is failingPossibly taken @shreyas-goenka claimed this today. Openbump-vuln-deps-failure
databricks/cli#7531 · 1 comment · 7 assignees ·
Maintainers usually reply within 1 day
-
bundle run on an app fails with "not in RUNNING state" when the app's compute is UPDATINGPossibly taken @andrewnester claimed this 1 day ago. OpenBug DABs
Difficulty 3/5 1-2 days Newbie friendliness 76/100
databricks/cli#7451 · 1 assignee ·
Maintainers usually reply within 1 day
-
Bundle deploy of an AI/BI dashboard breaks viewers' private bookmarks (UI save + publish does not)Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
databricks/cli#7419 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#6241 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coder/openstorage#807 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
NVIDIA/kubectl-nv#100 ·
Maintainers usually reply within 1 day
-
TestNoEagerPackageRegexps red on main: internal/gui/feedback.go:19 compiles a package-level regexpOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day