Uh oh!
There was an error while loading. Please reload this page.
Bump github.com/databrickslabs/terraform-provider-databricks from 0.5.8 to 0.6.0 - #7
Closed
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [github.com/databrickslabs/terraform-provider-databricks](https://github.com/databrickslabs/terraform-provider-databricks) from 0.5.8 to 0.6.0. - [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.8...v0.6.0) --- updated-dependencies: - dependency-name: github.com/databrickslabs/terraform-provider-databricks dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
ContributorAuthor
Superseded by #9. |
dependabotBot
deleted the
dependabot/go_modules/github.com/databrickslabs/terraform-provider-databricks-0.6.0
branch
June 20, 2022 11:50
yolocs pushed a commit
to yolocs/dbcli
that referenced
this pull request
Aug 11, 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: - **#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
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.8 to 0.6.0.
Release notes
Sourced from github.com/databrickslabs/terraform-provider-databricks's releases.
Changelog
Sourced from github.com/databrickslabs/terraform-provider-databricks's changelog.
Commits
94c9d75Release v0.6.0 (#1362)7bca37bAddeddatabricks_permissionsfordatabricks_pipeline(#1361)d15fecbAddedazure_managed_identityblock todatabricks_storage_credentialand `...f7c8d38Addednetwork_idtonetworkblock indatabricks_mws_workspacesfor GCP ...10d606cBump github.com/hashicorp/terraform-plugin-sdk/v2 from 2.16.0 to 2.17.0 (#1355)389ac98Bump github.com/stretchr/testify from 1.7.1 to 1.7.2 (#1356)afe1caaBump google.golang.org/api from 0.81.0 to 0.82.0 (#1357)a040fcbBump gopkg.in/ini.v1 from 1.66.5 to 1.66.6 (#1358)1f39f5eAddeddatabricks_git_credentialspat discovery from common environment vari...cdcb3e5Apply ownership for UC objects during creation (#1338)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)