Uh oh!
There was an error while loading. Please reload this page.
Bump github.com/databrickslabs/terraform-provider-databricks from 0.5.7 to 0.5.8 - #1
Merged
nfx merged 1 commit intoMay 23, 2022
Conversation
Bumps [github.com/databrickslabs/terraform-provider-databricks](https://github.com/databrickslabs/terraform-provider-databricks) from 0.5.7 to 0.5.8. - [Release notes](https://github.com/databrickslabs/terraform-provider-databricks/releases) - [Changelog](https://github.com/databrickslabs/terraform-provider-databricks/blob/master/CHANGELOG.md) - [Commits](databricks/terraform-provider-databricks@v0.5.7...v0.5.8) --- updated-dependencies: - dependency-name: github.com/databrickslabs/terraform-provider-databricks dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabotBotforce-pushed
the
dependabot/go_modules/github.com/databrickslabs/terraform-provider-databricks-0.5.8
branch
from
May 23, 2022 08:36
4c1a923 to
c83fb08Comparenfx
approved these changes
May 23, 2022
nfx
deleted the
dependabot/go_modules/github.com/databrickslabs/terraform-provider-databricks-0.5.8
branch
May 23, 2022 08:49
taiga-db pushed a commit
to taiga-db/cli
that referenced
this pull request
Oct 10, 2023
add lakehouse apps commands
9 tasks
2 tasks
5 tasks
10 tasks
pietern pushed a commit
that referenced
this pull request
May 8, 2026
Fix workspace client init after login, persist last profile
denik pushed a commit
that referenced
this pull request
May 20, 2026
Bumps [github.com/databrickslabs/terraform-provider-databricks](https://github.com/databrickslabs/terraform-provider-databricks) from 0.5.7 to 0.5.8. - [Release notes](https://github.com/databrickslabs/terraform-provider-databricks/releases) - [Changelog](https://github.com/databrickslabs/terraform-provider-databricks/blob/master/CHANGELOG.md) - [Commits](databricks/terraform-provider-databricks@v0.5.7...v0.5.8) --- updated-dependencies: - dependency-name: github.com/databrickslabs/terraform-provider-databricks dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Chambras pushed a commit
to Chambras/newDatabrickscli
that referenced
this pull request
Jul 6, 2026
…icks#5456) ## Why Originated from a customer case: `databricks ssh connect` to a dedicated cluster whose Docker container image was missing an OpenSSH **server** (`/usr/sbin/sshd`). The failure surfaced terribly — either a generic `server metadata error / metadata.json doesn't exist`, or the client just **hung** (the local `ssh` waited on its 360s `ConnectTimeout`). The root cause was buried in the cluster's job-run logs. This PR improves the diagnostics for `ssh connect` failures. ## What 1. **Surface bootstrap job-run errors.** When the SSH server bootstrap job reaches a terminal/failed state, fetch the run's state message, notebook error/trace, and run-page URL and show them — both when the task terminates before reaching RUNNING and when it dies after, during metadata polling. (`experimental/ssh/internal/client/client.go`) 2. **Guard against hangs when the server is up but the handshake never completes.** If the container image has no `sshd`, the server can't launch `/usr/sbin/sshd` on connect and **holds the websocket open**, so both proxy loops block forever. The client now runs the proxy loops in the background and aborts after a handshake timeout (no server response) with an actionable hint, and also exits promptly when the server *does* close the connection. (`experimental/ssh/internal/proxy/client.go`) 3. **openssh-server hint** when `ssh` exits with its connection-failure code (255). (`spawnSSHClient`) ## Tests - `client_internal_test.go`: failed-run message formatting (state message + trace + run URL), truncation, terminal-state detection (SDK mocks). - `proxy/client_server_test.go`: fast exit when the server closes the connection; abort on the handshake timeout when the server sends nothing. All `experimental/ssh/...` tests pass; lint clean. ## Status / follow-ups (WIP) - The missing-`sshd` path still incurs a ~30s handshake-timeout wait before failing. The cleaner fix is a **server-side pre-flight `sshd` check** (fail the bootstrap job immediately with a clear message), tracked separately — that would turn this case into an instant, clear job failure handled by improvement databricks#1. - The handshake timeout (30s) is conservative and currently a package constant; could be shortened or made configurable. - The proxy error and the outer 255 hint are slightly redundant; may consolidate. This pull request and its description were written by Isaac.
This was referenced Jul 7, 2026
rugpanov added a commit
that referenced
this pull request
Jul 10, 2026
Address review on the pipeline PR (concerns #1 and #2). Re-basing the merge on .bak silently discarded edits the user made to pyproject.toml between syncs: mergePlan used .bak as the merge base whenever one existed, so a re-run started from the pristine pre-sync original and any dependency the user added afterward was lost. MergeManaged rewrites only the three managed regions and is idempotent on its own output, so merging onto the live file yields identical managed regions without throwing away edits. - mergePlan now reads the live pyproject.toml as the merge base; .bak stays a one-time safety copy of the pre-sync original. - --check no longer reports a backup on a re-run (applyMerge keeps the existing .bak, so WouldBackup is set only when no .bak exists yet), and the diff is now against the live file, so an idempotent re-run reports no change — matching what a real run would do. - Replace TestPipelineRestoresBackupBeforeMerge (which encoded the old discard-edits behavior) with TestPipelineMergesOnLiveFileNotBackup, and add TestPipelineCheckReRunPlanMatchesRealRun. Also clarify the constraints-only comment: it stops managing the databricks-connect pin (greenfield dev = []; existing pin retained) rather than removing it, matching mergeDatabricksConnect's no-op-on-empty behavior. Co-authored-by: Isaac
varundeepsaini pushed a commit
to varundeepsaini/cli
that referenced
this pull request
Aug 17, 2026
## Changes Populates `warnings[]` in the `environments setup-local --output json` contract. It was declared but always empty, so the extension had no merge-quality signal (DECO-27787 had to omit `warningsCount`). Detection is a read-only compare of the pre-merge `pyproject.toml` against the fetched constraints (`detectMergeWarnings`); `MergeManaged` still owns the byte edits. Warnings fire for both `--dry-run` and real runs, and only for existing projects. **Codes:** - `W_REQUIRES_PYTHON_OVERRIDDEN` — the user's `requires-python` was replaced. - `W_DBCONNECT_PIN_OVERRIDDEN` — a `databricks-connect` pin in the dev group's own array was replaced. - `W_DBCONNECT_PIN_DUPLICATED` — the pin is reachable only through a PEP 735 `include-group`, which `MergeManaged` does not rewrite, so the env's pin is inserted *alongside* it. That leaves two pins for one package and `uv` cannot resolve. - `W_USER_CONSTRAINT_CONFLICT` — a user pin is provably outside the env's constraint for that package. ## Addresses review on databricks#6176 This is the `warnings` half of databricks#6176, split out per @anton-107's suggestion (the `durationMs` half is databricks#6190). All seven review items are addressed: - **databricks#1 (blocking)** — the indirect-pin case no longer claims "was replaced", which was factually untrue: the merge inserts a second pin rather than replacing anything. It now has its own code, `W_DBCONNECT_PIN_DUPLICATED`, since the user action differs (reconcile two pins by hand vs. nothing to do). - **databricks#2 (blocking)** — conflicts are now scanned in the dev group as well as `[project].dependencies`, following `include-group` references. `uv` applies `constraint-dependencies` to the whole resolution, so a group pin breaks `uv sync` identically. - **databricks#5 (blocking)** — disjointness is now decided by interval arithmetic over release ranges rather than a per-operator-pair table, so it decides the shapes the artifacts actually publish: opposite-direction bounds (`pyarrow<19` vs `>=20`), `~=` vs `~=`, and `~=` vs a bound. The main conflict test now uses `pyarrow<19` / `pandas<3` — matching the existing fixtures — instead of the `~=` shape that suited the old detector. - **databricks#3** — the dead `~=` branch is gone; the interval model replaced `clausesDisjoint`, `satisfies`, and `compatibleReleaseContains` entirely. The `parseClause` guard comment no longer cites a removed function. - **databricks#4** — `sortWarningsByMessage` removed. Warnings now come out in the user's declaration order; nothing upstream was ever unstable (`envByName` is only indexed, never iterated). - **databricks#6, databricks#7** — in databricks#6190. Inclusivity is tracked explicitly rather than normalizing to half-open ranges: releases have no successor, so turning `">3.12"` into `">=3.12.1"` would exclude `3.12.0.5`, which *does* satisfy it — and shrinking an interval can turn a real overlap into a false conflict. Anything not provably disjoint (`!=`, multi-clause, unparseable) still yields nothing; `uv` remains the real resolver. ## Tests `TestRangesDisjoint` gains the bound-vs-bound, `~=` vs `~=`, and endpoint-touching cases (`>=2.0` vs `<=2.0` overlaps on the shared version; `>2.0` vs `<=2.0` does not). New tests cover the duplicated-vs-overridden distinction, conflicts in the dev group and behind an `include-group`, and `include-group` cycles. **Not included:** the `merge-warnings-json` acceptance scenario from databricks#6176. Its golden contains a byte-exact `diff` field that has to be generated by running the suite, which I could not do — the SDK bump on main is undownloadable in my environment. Happy to add it in a follow-up, or if a reviewer regenerates goldens. _This pull request was written by Isaac._
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
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.
Bumps github.com/databrickslabs/terraform-provider-databricks from 0.5.7 to 0.5.8.
Release notes
Sourced from github.com/databrickslabs/terraform-provider-databricks's releases.
Changelog
Sourced from github.com/databrickslabs/terraform-provider-databricks's changelog.
Commits
1ca0ee5Release v0.5.8 (#1324)b1f8e90Addedtf:suppress_diffonartifact_locationfor `databricks_mlflow_experi...bc37c9bFix updatingdatabricks_service_principalon Azure (#1322)94a6474Updatedatabricks_mws_log_deliverydocs (#1320)8096cc8Clarify optionality ofdatabricks_mws_workspaces.deployment_namein docs ...b28d0ffBump github.com/hashicorp/terraform-plugin-sdk/v2 from 2.15.0 to 2.16.0 (#1313)5bb34c1Addedgcsdestination toinit_scriptsindatabricks_cluster(#1308)88e3a1eBump google.golang.org/api from 0.77.0 to 0.79.0 (#1310)789ae26Bump github.com/hashicorp/terraform-plugin-sdk/v2 from 2.14.0 to 2.15.0 (#1305)f8c02efRestrict KMS policy to caller AWS account (#1309)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)