Repository navigation
direct: retry transient errors when creating postgres resources - #7557
Merged
Merged
Conversation
Creating a postgres project sometimes fails with 500 INTERNAL_ERROR, either on the create request or on polling the create operation. DoCreate failures are not retried, unlike update and delete. - Poll the create operation again on transient errors for all postgres resources: the create request was accepted, so polling cannot duplicate it. - Mark a failed project create request as retry-safe: it is keyed by project_id, so a repeat cannot create a second project. cloud: TestAccept/bundle/resources/postgres_projects/basic TestAccept/bundle/resources/postgres_endpoints/basic Co-authored-by: Isaac <no-reply@databricks.com>
cloud: TestAccept/bundle/resources/postgres_projects/basic TestAccept/bundle/resources/postgres_endpoints/basic Co-authored-by: Isaac <no-reply@databricks.com>
cloud: TestAccept/bundle/resources/postgres_projects/basic TestAccept/bundle/resources/postgres_endpoints/basic Co-authored-by: Isaac <no-reply@databricks.com>
Contributor
|
Commit: Regression test reportSelected 1 changed tests (limit=20, 0 not selected) 6 tests: regression=2 unreleased=0 coverage=4 failing=0
TestAccept/bundle/resources/postgres_projects/create_transient_500/DMS=: branch ✅ | main (b69a249) ❌ | latest (v1.26.0) ❌main (b69a249): latest (v1.26.0): same output as main (b69a249) TestAccept/bundle/resources/postgres_projects/create_transient_500/DMS=true: branch ✅ | main (b69a249) ❌ | latest (v1.26.0) ❌main (b69a249): latest (v1.26.0): |
cloud: TestAccept/bundle/resources/postgres_projects/basic TestAccept/bundle/resources/postgres_endpoints/basic Co-authored-by: Isaac <no-reply@databricks.com>
Collaborator
✅ Integration test reportCommit: 37f3075
Top 18 slowest tests (at least 2 minutes):
|
denik
marked this pull request as ready for review
November 12, 2026 14:36
andrewnester
self-requested a review
November 12, 2026 18:14
andrewnester
left a comment
Contributor
There was a problem hiding this comment.
No blocking findings from a full pass; I'll take a manual look at the direct changes before approving.
andrewnester
approved these changes
Nov 13, 2026
Collaborator
❌ Integration test reportCommit: cf85b49
235 interesting tests: 154 MISS, 69 FAIL, 9 RECOVERED, 3 KNOWN
Top 50 slowest tests (at least 2 minutes):
|
idelafuente-oc
pushed a commit
to idelafuente-oc/cli
that referenced
this pull request
Nov 16, 2026
…atabricks#7641) ## Changes Record postgres requests with `print_requests.py --unique` in `bundle/resources/postgres_endpoints/update_autoscaling`, so a retried request (an identical consecutive request) is recorded once. ## Why On GCP the backend returned a transient 500 for `GET .../branches/main` during the no-change deploy. The CLI retried the read on purpose (`libs/retry`, `IsTransientRead` in `bundle/direct`), and the retry showed up as an extra request in `out.requests.no_change.json`. The retry is correct behavior, so the recording should tolerate it. Same approach as databricks#7511 and databricks#7547 for apps. Not a regression from databricks#7557 (that change retries create-operation polling) or from databricks#7596 (testserver spec echo). The failing request is a plain remote-state read that has been retried for a while. The current goldens have no consecutive duplicate requests, so `--unique` changes only the traced command line in output.txt. ## Dashboard - [TestAccept/bundle/resources/postgres_endpoints/update_autoscaling/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_endpoints/update_autoscaling/DMS=true?main=1&pr=1&end=2026-11-15T03:00:00Z&last=2d) - [error/3462](http://go/cli/dashboard/error/3462?main=1&pr=1&end=2026-11-15T03:00:00Z&last=2d) ``` Suppressed from output.txt: Warn: retrying after 500 Internal Server Error from GET /api/2.0/postgres/projects/test-pg-proj-[UNIQUE_NAME]/branches/main ... +{ + "method": "GET", + "path": "/api/2.0/postgres/projects/test-pg-proj-[UNIQUE_NAME]/branches/main" +} Messages: bundle/resources/postgres_endpoints/update_autoscaling/out.requests.no_change.json ``` ## Tests Passed locally and on AWS (both DMS variants). The last commit asks CI to run the test on GCP and AWS. This pull request and its description were written by Isaac. Co-authored-by: Isaac <no-reply@databricks.com>
This was referenced Nov 17, 2026
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Nov 19, 2026
## Release v1.27.0 ### Notable Changes * `databricks aitools install`, `update` and `uninstall` now exit with code 1 when they do nothing they were asked to. `install` fails when it sets up nothing: no coding agent is detected, every agent is skipped or fails to install, or no skill in the release can be installed (also with `--path`). `update` fails when every update or check it attempts fails, and `uninstall` when every removal it attempts fails. Scripts that ran these commands as a best-effort step and relied on exit code 0 should handle the new exit code. ([#7481](#7481)) * Add `file:<path>` selectors to `pipelines run` and pipeline `bundle run`. `--refresh` and `--full-refresh` now use space-separated lists, such as `--refresh "orders payments"`, instead of comma-separated lists. Single names containing spaces now require backticks, e.g. ``--refresh 'table:`order details`'``. ([#7184](#7184)) * The Databricks CLI is now available on PyPI as `databricks`: run it with `uvx databricks`, or install it with `uv tool install databricks`, `pipx install databricks` or `pip install databricks`. The package contains only the prebuilt CLI binary. Uninstall the legacy `databricks-cli` package first, since both install a `databricks` command. ([#7704](#7704), [#7777](#7777)) ### CLI * Add `databricks sandbox fs` commands (`cp`, `ls`, `cat`, `mkdir`, `rm`) to transfer files between your local filesystem and sandboxes using `<sandbox-id>:/path`. ([#7372](#7372)) * `databricks fs` commands retry reads (stat, list, open) and deletes on DBFS and Volumes when the server returns a transient error or does not respond within the HTTP timeout. ([#7556](#7556)) * Retry UC Volumes file operations (`fs cp`, `fs ls`, `fs rm`, bundle uploads to Volumes) when the Files API returns HTTP 408, 429, 502, 503 or 504 (for example "AWS S3 is throttling requests"), or on a transient network error; this regressed in v1.10.0. ([#7559](#7559)) * Stop warning when the host metadata request (`/.well-known/databricks-config`) times out; the CLI already falls back to your config, and the message is still shown with `--debug`. ([#7752](#7752)) * Add `databricks aitools auto-install disable` and `enable` to turn off (or back on) the automatic installation of Databricks AI tools on CLI upgrades. A global-scope `databricks aitools uninstall` also turns it off. ([#7701](#7701)) * Stop printing the Databricks AI tooling install hint on `auth`, `configure`, `current-user me`, `version`, `help`, and shell-completion commands. ([#7452](#7452)) * When Codex, Cursor, GitHub Copilot CLI, OpenCode, Gemini CLI, Antigravity, Pi, Goose or Kiro run the CLI without Databricks skills installed for that agent, the CLI now prints a one-line hint to install them with `databricks aitools install --agents <agent> --scope global`, previously shown only to Claude Code. ([#7586](#7586)) * `databricks aitools install` now rejects an unknown `--agents` name before it shows the scope prompt, instead of after. ([#7469](#7469)) * `databricks aitools install` no longer asks "Proceed?" after the agent picker; the picker selection confirms the plan. The picker title now shows the install scope, its hint says Enter installs, `--skills-only` runs label plugin agents "skills" and pre-check every agent whose config dir exists, and the plan summary after it is reduced to the scope line. ([#7478](#7478)) * `databricks aitools install --output json` reports more specific `error_category` values: `SKILLS_FETCH_FAILED`, `RELEASE_LOOKUP_FAILED`, `RATE_LIMITED`, `MANIFEST_INVALID`, `STATE_INVALID` and `PLUGIN_CLI_TIMEOUT`. A coding agent CLI that does not answer in time is now reported as `timed out after <duration>`, followed by any stderr it wrote before it was stopped. ([#7475](#7475)) * `databricks aitools install` no longer prompts when a coding agent runs it, even in a pseudo-terminal; it uses the non-interactive defaults instead and prints a note saying so. ([#7477](#7477)) * `databricks aitools install` now prints the directory it installed skills into (for example `Installed 1 skill in ~/.databricks/aitools/skills.`), so agents can open the installed `SKILL.md` files without searching for them. ([#7668](#7668)) * `databricks aitools install` now ends a failed install with a step to recover, in the text output and in a new `recovery` field of `--output json`. ([#7480](#7480)) * `databricks aitools install` now installs plugins for the other coding agents even when installing skill files fails. ([#7479](#7479)) * `databricks aitools install` now installs skill files for a detected coding agent whose CLI is not on PATH (for example a Claude Code desktop or IDE install), unless it already has the plugin, says how to switch to the plugin later, and warns when the current project also has the plugin. `databricks aitools update` no longer tries to install the plugin for such an agent, and no longer writes skill files next to a plugin that such an agent already has. ([#7482](#7482)) * Fix `databricks aitools install` waiting a long time on an unreachable or slow workspace while it resolves authentication for telemetry; that wait is now limited to a few seconds. ([#7468](#7468)) * `databricks aitools install`, `update` and `list` now refuse a skills manifest that names a skill or file outside the skills directory, before writing any skill files. A skill whose name or file paths are not portable is skipped with a warning, and `update` keeps its installed copy. ([#7722](#7722)) * `databricks aitools install` and `databricks aitools update` refresh only the marketplace the Databricks plugin is listed in, so another unreachable marketplace no longer blocks them. When that refresh fails, both commands warn, install or update the plugin from the local copy of the marketplace, and record the plugin version as unknown. ([#7473](#7473)) * `databricks aitools install` and `databricks aitools update` now wait up to 20 seconds instead of 5 for a coding agent's CLI to answer the plugin capability check, so a slow first start is less likely to report the agent as unavailable. ([#7472](#7472)) * `databricks aitools install` no longer fails a plugin-only install when the lookup of the latest skills release on GitHub fails or is rate-limited. The plugin is installed and its version is recorded as unknown. ([#7474](#7474)) * `databricks aitools` commands now send usage telemetry, and the CLI records when it recommends installing Databricks AI tools. When the configured workspace is slow or unreachable, `aitools install`, `update` and `uninstall` can take up to about 6 seconds longer, and `list`, `version` and runs that stop early up to about 3 seconds. Set `DATABRICKS_CLI_DISABLE_TELEMETRY=1` to opt out. ([#7467](#7467), [#7469](#7469), [#7470](#7470)) * `databricks aitools install` and `databricks aitools update` now report a coding agent CLI shim (`.cmd` or `.bat`) on Windows that prints its plugin help and then exits with an error as `shim-exited-with-error`, with the command to run to see the error, instead of reporting the CLI as not on PATH. ([#7476](#7476)) * `apps init` no longer suggests installing skills when every detected coding agent already has the Databricks plugin. ([#7467](#7467)) * `databricks auth login` now gives up on the optional workspace lookup after about 5 seconds instead of retrying for about 5 minutes, and explains the fallback to the manual workspace ID prompt. ([#7522](#7522)) * Throttle Claude Code's native plugin install hint separately from the text hint: it prints at most once per 10 minutes per session, so the install dialog still comes up when a subagent, a hook, or a command outside a Claude Code subprocess runs the session's first `databricks` command. ([#7692](#7692)) * Print Claude Code's native plugin install hint alongside the text hint, so Claude Code offers a one-click install of the Databricks plugin. Claude Code now counts as having the tooling only when it loads it: skills only in `~/.databricks/aitools/skills` don't count, and a project- or local-scope plugin counts only when the CLI runs inside that project. `auth token`, `auth docker token` and CLI subprocesses no longer print install hints. ([#7585](#7585)) * Interactive prompts and pagers now work in Git for Windows' bash and other MSYS2 shells when they run under ConPTY (the default since Git for Windows 2.47) or directly in a Windows console. ([#7699](#7699)) * Add the `databricks feedback` command to send feedback about the CLI to Databricks. ([#7724](#7724)) * Fix shell completion in `databricks fs` commands for local paths typed with a leading `./` or repeated separators, which previously offered no suggestions. ([#7679](#7679)) * Fix a panic in `databricks labs` commands when a non-string SDK setting such as `DATABRICKS_DEBUG_HEADERS` or `DATABRICKS_RATE_LIMIT` is set in the environment. ([#7673](#7673)) * Fix a panic in `databricks labs install` for projects whose `labs.yml` has no `install` section. ([#7673](#7673)) * `NO_COLOR` no longer disables prompts, spinners or the list pager; they run without color. ([#7700](#7700)) * Add the Beta `databricks pipelines test` command, which runs the tests of a pipeline, and the `testing` property of pipelines in bundles. ([#7429](#7429)) * Add `databricks sandbox forward`, which serves an app running in a sandbox at a local URL. ([#7395](#7395)) * Bound the whole telemetry upload at exit, including config resolution and authentication, by its timeout, so a stalled auth or telemetry endpoint no longer keeps a command from exiting. ([#7467](#7467)) * `databricks version --check` now suggests `databricks aitools install` on stderr when a coding agent is detected without the Databricks plugin or skills. ([#7471](#7471)) ### AI Runtime * `air get -o json` now reports `PENDING` while the run waits for compute, matching `air list`, and includes the run's `status_message`. ([#7455](#7455)) * Wrap long failure reasons and log lines in the `air list` info and logs panes, keep the MLflow link (labeled with its retry) when a run's last retry failed before starting, and point `air logs` at earlier retries when the last one has no logs. ([#7456](#7456)) * `databricks air logs --node` now reports an out-of-range node index when it can determine the run's node count, instead of looking like a successful run with no logs. ([#7516](#7516)) * Add experiment, duration, accelerator, and dashboard metadata to `air list --output json`. For retried runs, `started_at` now reports the latest attempt, matching `air get`. ([#7568](#7568)) * `air list` shortens MLflow run names and unnamed-run IDs by keeping their end behind a leading `…`, and its columns no longer overflow on wide (for example CJK) text; `air get` shows an unnamed run's full MLflow run ID. ([#7582](#7582)) * Shrink the Experiment and User columns of the interactive `air list` table to fit the terminal width, keeping the end of a shortened experiment name. ([#7583](#7583)) * Show the experiment, accelerators and configuration in the `air list` info pane for runs where it showed `N/A`. ([#7587](#7587)) * Strip terminal control characters from the MLflow run, experiment and user names shown by `air list` and `air get`, so a run name cannot clear or retitle the terminal of whoever lists it. ([#7601](#7601)) * `air logs`, `air get`, and `air run --watch` no longer make an extra credential-check request before fetching the run, and `air get` reuses the configured workspace ID instead of looking it up. ([#7613](#7613)) * `air list` no longer waits on extra current-user requests before listing runs, which makes the default list about 150ms faster. ([#7615](#7615)) * `air list --all-status` requests larger index pages, so it makes far fewer round trips once the server supports `page_size`. ([#7616](#7616)) * Fit the interactive `air list` table to narrow terminals: when the Experiment and User columns are at their floors, shorten Started to `MM-DD HH:MM` and size the MLflow column to its labels, then hide Accelerators, User, MLflow and Progress in that order, naming the hidden columns in the hint line. ([#7629](#7629)) * `air get -o json` now includes `mlflow_run_id` and `mlflow_experiment_id`, so a run can be handed to MLflow-based steps without parsing `mlflow_url`. They identify the MLflow run `mlflow_url` links to, including one from an earlier retry that `mlflow_retry` names. ([#7636](#7636)) * `air get` and the `air list` info pane now show the environment of runs on the Databricks AI environment (`databricks_ai_v*`) instead of `N/A`. ([#7637](#7637)) * `air run` now rejects a `code_source.include_paths` path that selects no files instead of uploading a snapshot without it; glob patterns and pathspec magic are left to git. ([#7643](#7643)) * `air convert-to-dabs` now suggests the `--output-dir` that converts a working-tree workload whose `code_source.root_path` is outside the bundle directory, instead of suggesting `sync.paths`. ([#7644](#7644)) * `air run` now lists a `code_source.root_path` outside a git repository relative to `root_path`, so running from a subdirectory of `root_path` no longer uploads an empty or partial snapshot. ([#7646](#7646)) * `air list --all-status` now fills `--limit` past purged or inaccessible indexed runs. ([#7743](#7743)) * `air run` now warns about missing PyTorch when a pinned snapshot's `include_paths` selects a Python file. ([#7744](#7744)) * `air cancel JOB_RUN_ID` now rejects run IDs that are not AI Runtime runs instead of cancelling unrelated Jobs runs. In `-o json` output, the `failed[].error` text for a run that does not exist or that you cannot view now starts with `failed to get run <id>:` instead of the cancel API error. ([#7569](#7569)) * `air get -o json` now reports `mlflow_retry` when the MLflow link comes from an earlier retry because the run's last retry never reached MLflow. ([#7620](#7620)) * `databricks air run --help` now shows how to install the databricks-ai-runtime coding agent skill. ([#7652](#7652)) * `air run --watch -o json` now reports each lifecycle `STATUS` transition once and never reports a non-terminal state after the run has ended, including when logs are served from MLflow artifacts. ([#7621](#7621)) * `air convert-to-dabs` now explains the `--output-dir` workaround when `code_source.root_path` resolves to the bundle root, and notes when the generated job carries the default `max_retries`. ([#7579](#7579)) * `air run` now refuses to upload a `code_source` snapshot that selects no files (for example when `root_path` is git-ignored) and explains the cause, and `--dry-run` runs the snapshot file selection and reports the file count. ([#7570](#7570)) * Repeat the Jobs run link after live log streaming ends. ([#7571](#7571)) * `air get -o json` includes run details including flat `accelerator_type` and `num_accelerators`. Use `--include-config` to include stored config, which may contain plaintext `env_variables` and parameters; downloads over 1 MiB are omitted, and config-dependent `max_retries` is otherwise null. ([#7624](#7624)) * `air get` and the `air list` info pane no longer show `Max Retries 0` when the Jobs API leaves the task's retry limit out. For a run submitted with `air run`, the limit now comes from the run's uploaded config, shown as `3 (CLI default)` when the config doesn't set `max_retries`; it shows `N/A` when the limit can't be known (job runs, multi-container runs, legacy runs with no explicit value, or an unreadable config). ([#7623](#7623)) * Reorganize `databricks air` help: subcommands are grouped by task, `air run` has examples, and YAML fields are listed under headings, with pool fields marked optional and `command`, `compute.num_accelerators`, and `compute.accelerator_type` correctly marked required. ([#7512](#7512)) * `air run -h config` now lists the environment variables AI Runtime sets on every node (such as `MLFLOW_RUN_ID` and `CODE_SOURCE_PATH`), and `air logs --help` notes that `--download-to` cannot be combined with `--tail` or `--minutes`. ([#7655](#7655)) * Support full workspace accelerator types in `air list` filters while preserving family matching, and reject invalid filter values. ([#7515](#7515)) * `databricks air list --all-status` now warns when the AI Runtime run index is unavailable and it falls back to scanning Jobs runs. That fallback scan is capped at 250 runs, and a stuck index request fails after 15 seconds instead of retrying for minutes. `--all-status --filter user=<your email>` now uses the run index instead of scanning the workspace's full run history. ([#7619](#7619)) * Return structured JSON errors for invalid `air list --filter` values when `-o json` is used. ([#7612](#7612)) * `air list --all-status` no longer fails when a listed run has been purged. ([#7523](#7523)) * **Behavior change:** `databricks air logs` now prints the logs available now and exits, also for an active run, matching `kubectl logs`, `docker logs` and `databricks apps logs`. Pass `--follow` (`-f`) to stream new lines until the run completes; `--tail N --follow` prints the last N lines first. `databricks air run --watch` still submits and streams. ([#7658](#7658)) * `databricks air logs -o json` and `databricks air run --watch -o json` now emit a `WAITING` event, for example `{"type":"WAITING","message":"Waiting for accelerator compute capacity..."}`, when the reported waiting status changes. ([#7695](#7695)) * `databricks air logs` on a run that ended in the last two minutes now waits for the log index to settle before printing, instead of sometimes dropping lines that were indexed late. ([#7663](#7663)) * `air logs` and `air run --watch` now print the waiting status (for example `Waiting for accelerator compute capacity...`) as a line on stderr when stderr is not a terminal, instead of printing nothing until the run produces logs. ([#7657](#7657)) * Route AIR log links to the MLflow Logs page instead of the hidden artifact path. ([#7491](#7491)) * Invalid `compute.accelerator_type` errors and `air run -h config.compute` no longer list the CLI's built-in accelerator types, which could differ from the workspace's. ([#7520](#7520)) * `databricks air --help` now notes that GPU pools are not required to run workloads. ([#7581](#7581)) * `air run` now prints the job run URL with the `?o=<workspace-id>` suffix, matching `air get` and `air list`; `dashboard_url` in `air run -o json` and the `--watch` events gains it too. When `air list` cannot resolve the workspace ID, its links now omit `?o=` instead of ending in `?o=0`. ([#7573](#7573)) * `databricks air run` now reports an unknown workload YAML key by its field path, suggests the closest valid field, and points to `-h config` instead of naming an internal Go type. ([#7574](#7574)) * `air run` (including `--dry-run`) now warns before submitting when the `code_source` imports `torch` but PyTorch is not declared: the environment is the Standard environment (version 5 or later) with no `torch` dependency, so the run may fail after it waits for a GPU. ([#7656](#7656)) ### Bundles * Add `isolation_mode` to the `catalogs` resource, so a catalog can be deployed as `OPEN` or `ISOLATED`. ([#7463](#7463)) * `bundle validate` no longer warns when resource permissions and top-level or target permissions name the same principal. ([#7291](#7291)) * Retry bundle file uploads, reads and deletes when the server does not respond within the HTTP timeout ("request timed out after ... of inactivity"). ([#7521](#7521)) * Show how to recover when `bundle deploy` fails because an app's service principal does not exist or was deleted. ([#7533](#7533)) * Retry transient server errors when creating Lakebase (`postgres_*`) resources in the direct deployment engine. ([#7557](#7557)) * Fix `bundle plan` reporting the `spark_conf` and `custom_tags` the backend derives from `is_single_node: true` as drift on clusters. ([#7577](#7577)) * Stop planning a spurious update for Lakeflow Connect pipelines whose `ingestion_definition.data_staging_options` is filled in by the backend. ([#7603](#7603)) * Retry the root path check in `bundle destroy` on transient errors, so a dropped connection no longer fails the destroy. ([#7597](#7597)) * Use the Lakebase branch when its create request times out but the branch was created, instead of failing the deploy, in the direct deployment engine. ([#7602](#7602)) * Retry transient server errors when deleting resources in the direct deployment engine. ([#7708](#7708)) * Use the Lakebase project when its create request times out but the project was created, instead of failing the deploy with "already exists", in the direct deployment engine. ([#7747](#7747)) * Use the feature, model serving endpoint or dashboard that a create request created despite timing out, instead of failing the deploy, in the direct deployment engine. ([#7757](#7757)) * Use the Lakebase role when its create request fails with a transient error but the role was created, instead of failing the deploy, in the direct deployment engine. ([#7767](#7767)) * Use the MCP service, model service or model provider service that a create request created despite failing with a timeout, a 499 or a reset stream, instead of failing the deploy, in the direct deployment engine. Create recovery for features, serving endpoints and dashboards now also covers 499 and reset streams. ([#7782](#7782)) * Retry app updates and deletes in the direct deployment engine when they fail with 400 BAD_REQUEST because the app compute is `UPDATING`, after waiting for the compute to settle. ([#7606](#7606)) * Enable drift detection for `source_code_path` and `git_source` on apps. ([#6399](#6399)) * `bundle destroy` and `bundle deploy` no longer fail with "internal error, missing in state" when the state holds an empty-ID entry left by an interrupted recreate in an older CLI. ([#7676](#7676)) * Fix a feature whose `full_name` contains uppercase letters being recreated on every deploy. ([#7398](#7398)) * Fix `bundle deployment bind` (and `bundle generate --bind`) failing with `no such node "resources.internal_immutable_snapshots.immutable"` when `workspace.sync_mode` is `immutable`, as reported in [#7306](#7306). ([#7329](#7329)) * Retry creating the deployment lock (without `--force-lock`) when the request fails with a transient server error, times out ("request timed out after ... of inactivity") or loses its connection ("unexpected EOF"). ([#7594](#7594)) * Fix a materialization set member whose `feature_name` contains uppercase letters failing to deploy, or recreating the set on every deploy. ([#7398](#7398)) * Delete the old resource when its name follows a renamed schema. ([#7718](#7718)) * Fix `pipelines dry-run` starting a real run when given a job KEY, and a crash in its shell completion. ([#7672](#7672)) * Rename schemas in place; schemas and volumes follow a renamed catalog or schema. ([#7343](#7343)) * Fix a panic when validating or deploying jobs with local libraries and serverless job clusters. ([#7725](#7725)) * Fix `tgz` artifacts with `git` set producing an empty tarball or failing when the bundle is in a subdirectory of the git repository. ([#7674](#7674)) * Apply `presets.trigger_pause_status` and the development mode pause default to `triggers[]` entries on jobs. ([#7450](#7450)) ### Dependency Updates * Bump dependencies with known vulnerabilities. ([#7750](#7750)) * Update the Go SDK to [v0.198.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.198.0). ([#7530](#7530)) * Update the Go SDK to [v0.199.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.199.0). ([#7584](#7584)) * Update the Go SDK to [v0.200.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.200.0). ([#7653](#7653)) * Update the Go SDK to [v0.201.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.201.0). ([#7769](#7769))
idelafuente-oc
pushed a commit
to idelafuente-oc/cli
that referenced
this pull request
Nov 20, 2026
## Changes `bundle destroy` in the direct engine now retries a resource's delete on transient server errors (5xx without SDK retry, 408, inactivity timeout), using the existing `libs/retry` policy (2 retries, 15s apart). `DeploymentUnit.Delete` wraps `DoDelete` in `retry.With(ctx, retry.IsTransient, ...)`, as `Recreate`, `Update`, `UpdateWithID` and `Resize` already do. Before this change it was the only apply path that did not retry. A repeated delete is safe: if the failed attempt did delete the resource, the retry gets a NotFound, which `Delete` already treats as success. Judgment calls: - The fix is in the generic `Delete` path rather than in the postgres resource, because every other mutating call there already retries this way and the failure is not postgres-specific. - `DoDelete` for postgres also waits on the delete operation; a 500 on that poll now re-issues the delete as well. That matches what `Recreate` already does with the same `DoDelete`. ## Why Cloud integration runs on main hit a 500 from the Lakebase API on `DELETE /api/2.0/postgres/projects/...` during `bundle destroy`. Both failures passed on the test runner's second attempt, so the error is transient. databricks#7557 added retries for postgres creates; delete during destroy was left without one. Dashboard: | error | snippet | |---|---| | [error/3326](http://go/cli/dashboard/error/3326?main=1&pr=1&end=2026-11-17T07:00:00Z&last=7d) | `Error: cannot delete resources.postgres_projects.my_project: deleting id=projects/test-pg-proj-[UNIQUE_NAME]: The request could not be processed. Please try again later and contact Databricks if the problem persists. [TraceId: [TRACE_ID]] (500 INTERNAL_ERROR)` on `DELETE [DATABRICKS_URL]/api/2.0/postgres/projects/test-pg-proj-[UNIQUE_NAME]` | Affected tests (GCP): [postgres_catalogs/recreate/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_catalogs/recreate/DMS=true?main=1&pr=1&end=2026-11-17T07:00:00Z&last=7d), [postgres_synced_tables/recreate/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS=true?main=1&pr=1&end=2026-11-17T07:00:00Z&last=7d). ## Tests - New local acceptance test `bundle/resources/postgres_projects/delete_transient_500`: the testserver deletes the project and then returns a 500 (`fault.py --after-handler`). Without the fix, destroy fails with the same error as on cloud. With it, the retried DELETE gets a NotFound, which counts as deleted, and destroy succeeds (two DELETE requests recorded). - Full local `TestAccept/bundle` suite passes. - The last commit asks CI to run both affected tests on GCP. This pull request and its description were written by Isaac. --------- Co-authored-by: Isaac <no-reply@databricks.com>
idelafuente-oc
pushed a commit
to idelafuente-oc/cli
that referenced
this pull request
Nov 20, 2026
…tabricks#7602) ## Changes When the request to create a postgres branch fails with a transient error (5xx, 408, inactivity timeout), the direct engine now looks for the branch before giving up. It repeats the request while the branch is missing: - **The branch exists and our request created it:** if it is `READY`, use it. If it is `INIT`, wait for `READY` (up to 10 minutes); if the wait ends early, use it anyway, with a warning, so state records it. In any other state (`DELETED`, `ARCHIVED`, ...), fail with the original error. - **The branch exists but predates our first request** (by `create_time`, allowing a minute of clock skew): fail with the original error. It isn't taken over. - **The branch is missing:** pause for the standard retry interval, then repeat the create, up to `retry.MaxRetries` times. A repeat that fails with `ALREADY_EXISTS` means the earlier request has landed in the meantime; the next look finds that branch and uses it. - **`replace_existing: true`:** the error is marked `retrySafe`, and `DeploymentUnit.Create` repeats the create without reading the branch. A branch found at this point may predate the request, and repeating a replace is safe. - A read of the branch that fails returns the original create error, with the read error as a warning. A cancelled context is returned as is. `libs/retry` gains `Pause`, the log-and-wait step of `retry.With`, which the loop above uses so its retries print the usual `retrying after ...` warning. Follow-up to [databricks#7557](databricks#7557), which retried transient errors while polling create operations and on the project create request. Branches were left out there because they weren't failing yet. Judgment calls: - The wait for `READY` stays inline in `DoCreate`, as the create-operation wait on the success path does, rather than moving to `WaitAfterCreate`. The latter would read every created branch once more, for a path that only runs after a failed create. - Using a recovered branch is logged at Info, not Warn: the deploy got the branch it asked for, and acceptance goldens stay the same when a cloud deploy recovers. - Only branches are changed. Projects have no ready state to wait for, and their create request was already made retry-safe in [databricks#7557](databricks#7557). ## Why The Lakebase API sometimes answers a branch create with a 504 that says the branch may still be created. The deploy failed even when the branch had been created, and dependent resources failed with it. Dashboard: | error | snippet | |---|---| | [error/3325](http://go/cli/dashboard/error/3325?main=1&pr=1&end=2026-11-13T11:00:00Z&last=7d) | `Error: cannot create resources.postgres_branches.main: The create request timed out and may still be completing. Check whether the resource was created before retrying. (504 DEADLINE_EXCEEDED)` on `POST [DATABRICKS_URL]/api/2.0/postgres/projects/test-pg-proj-[UNIQUE_NAME]/branches?branch_id=main` | Tests: [postgres_databases/update/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_databases/update/DMS=true?main=1&pr=1&end=2026-11-13T11:00:00Z&last=7d), [postgres_roles/replace_existing/DMS=](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_roles/replace_existing/DMS=?main=1&pr=1&end=2026-11-13T11:00:00Z&last=7d). ## Tests - New unit tests in `bundle/direct/dresources/postgres_branch_test.go` drive `DoCreate` against a testserver with scripted responses. They cover every recovery path: `INIT` then `READY`, `INIT` past the timeout, `DELETED`, a failed read, a cancelled context, `replace_existing`, a non-transient error, a repeat that succeeds, a repeat that gets `ALREADY_EXISTS`, a branch that stays missing, and a branch that predates the request. - New local acceptance test `bundle/resources/postgres_branches/create_504`, with four 504 scenarios: - the branch was created: it is used; - it was not created: the create is repeated; - the read fails: the deploy fails with the original error; - `replace_existing`: the create is repeated without a read. - The existing local `bundle/resources/postgres_*`, `bundle/deploy`, `bundle/upload`, `bundle/sync` and `bundle/resources` acceptance tests, and the `bundle/direct/...` and `libs/retry` unit tests, pass. - The last commit asks CI to run `postgres_branches`, `postgres_roles/replace_existing` and `postgres_databases/update` on every cloud. This pull request and its description were written by Isaac. --------- Co-authored-by: Isaac <no-reply@databricks.com>
idelafuente-oc
pushed a commit
to idelafuente-oc/cli
that referenced
this pull request
Nov 20, 2026
…atabricks#7747) ## Changes When the request to create a postgres project fails with a transient error (5xx, 408, inactivity timeout), the direct engine now looks for the project before repeating the request, as [databricks#7602](databricks#7602) does for branches: - **The project exists and our request created it** (by `create_time`, allowing a minute of clock skew): wait for its default branch to leave `INIT`, as the create operation on the success path would have, then use the project and log that at Info. A wait that times out, or a default branch that can't be read, only warns: the project is ours, so state records it. - **The project exists but predates our first request:** fail with the original error plus `project ... exists but was not created by this deployment`. It isn't taken over. - **The project is missing:** pause for the standard retry interval (with the usual `retrying after ...` warning), then repeat the create, up to `retry.MaxRetries` times. A repeat that fails because the project already exists means the earlier request has landed in the meantime; the next look finds that project and uses it. - A read that fails returns the original create error, with the read error as a warning. A cancelled context is returned as is. Before this PR, the project create error was marked `retrySafe` ([databricks#7557](databricks#7557)) and `DeploymentUnit.Create` repeated the request without looking. When the 504'd request had created the project, the repeat failed with "already exists", and the deploy failed. The look-then-repeat loop from `postgres_branch.go` moves to `postgres_create_recovery.go` (`recoverPostgresCreate`) and both resources use it. Branch behavior is unchanged; its unit tests and `create_504` acceptance test pass as before. The real API answers a duplicate project create with `400 BAD_REQUEST` "A project with this resource name already exists in the workspace.", not `409 ALREADY_EXISTS` (branches use 409). The loop accepts both (`isPostgresAlreadyExists`), and `libs/testserver` now answers a duplicate project with the same 400 as the cloud. Judgment calls: - Projects have no ready state of their own, so the recovered project waits on its default branch, reusing the branch's `INIT` wait (`waitBranchReady`). - The "already exists" check is shared, so a repeated branch create that gets a 400 mentioning "already exists" now also goes back to the lookup instead of failing at once. The result is the same (a branch is used only if found and created by this deploy), with at most `retry.MaxRetries` extra requests. - Without `project_id`, a failed create is not repeated any more: there is no name to look up, and the API rejects such a request with 400 anyway (`without_project_id/out.deploy.txt`). ## Why On Azure, a project create was answered with a 504 after the project had been created. The retry then hit "already exists" and the deploy failed, along with every test that deploys a project first. Dashboard: | error | snippet | |---|---| | [error/3516](http://go/cli/dashboard/error/3516?main=1&pr=1&end=2026-11-18T05:00:00Z&last=2d) | `Warn: deploying resources.postgres_projects.my_project: retrying after 504 Gateway Timeout from POST /api/2.0/postgres/projects` then `Error: cannot create resources.postgres_projects.my_project: A project with this resource name already exists in the workspace. [TraceId: [TRACE_ID]] (400 BAD_REQUEST)` | Tests: [postgres_databases/recreate/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_databases/recreate/DMS=true?main=1&pr=1&end=2026-11-18T05:00:00Z&last=2d), [postgres_projects/add_default_endpoint_settings/DMS=](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_projects/add_default_endpoint_settings/DMS=?main=1&pr=1&end=2026-11-18T05:00:00Z&last=2d), [postgres_projects/purge_on_delete/DMS=](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_projects/purge_on_delete/DMS=?main=1&pr=1&end=2026-11-18T05:00:00Z&last=2d), [postgres_snapshot_schedules/basic/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_snapshot_schedules/basic/DMS=true?main=1&pr=1&end=2026-11-18T05:00:00Z&last=2d). ## Tests - New unit tests in `bundle/direct/dresources/postgres_project_test.go` drive `DoCreate` against a testserver with scripted responses: the project is found and used; missing then a successful repeat; missing then a repeat that gets the 400 "already exists", then the project is found; missing on every attempt; a project that predates the request; a failed read; a non-transient error (no read); no `project_id` (no read, no repeat); the default branch in `INIT` then `READY`; a default branch that can't be read. - New local acceptance test `bundle/resources/postgres_projects/create_504`: the project was created despite the 504 and is used (one POST, the project GET and its default branch GET); the read fails and the deploy fails with the original 504. - `postgres_projects/create_transient_500` now records the GET before the repeated POST. - The local `bundle/resources/postgres_*` and `bundle/deploy` acceptance tests and the `bundle/direct/...`, `libs/retry` and `libs/testserver` unit tests pass. - The last commit asks CI to run `postgres_projects`, `postgres_databases/recreate` and `postgres_snapshot_schedules/basic` on Azure. This pull request and its description were written by Isaac. --------- Co-authored-by: Isaac <no-reply@databricks.com>
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 free
to 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.
Changes
Creating postgres (Lakebase) resources in the direct engine now retries transient server errors:
GET .../operations/...) is retried on transient errors (5xx, 408, inactivity timeouts) for every postgres resource. The create request was already accepted, so polling again cannot create a duplicate. A new helper,waitCreateOperation, wrapswaiter.Waitwithretry.IsTransientRead.POST /api/2.0/postgres/projects) is markedretrySafe, soDeploymentUnit.Createretries it on transient errors. The request is keyed by the caller-chosenproject_id, so a repeat cannot create a second project. If the failed request did create the project, the retry fails withALREADY_EXISTS, which is the same error the next deploy would have hit.Update and delete were already retried as a whole in
apply.go. Before this change, a create failure was returned without retrying.Judgment calls:
libs/retrypolicy: 2 retries, 15s apart.Why
Cloud integration runs on main hit 500s from the Lakebase API when creating a project, both on the create request and on the operation poll. These are 9 failures across 7 tests in 7 days on AWS and GCP. Most passed on the test runner's second attempt, so the errors are transient.
Dashboard:
Error: cannot create resources.postgres_projects.my_project: The request could not be processed. Please try again later and contact Databricks if the problem persists. [TraceId: [TRACE_ID]] (500 INTERNAL_ERROR)onPOST [DATABRICKS_URL]/api/2.0/postgres/projects?project_id=test-pg-proj-[UNIQUE_NAME]orGET [DATABRICKS_URL]/api/2.0/postgres/projects/test-pg-proj-[UNIQUE_NAME]/operations/...Affected tests: postgres_endpoints/basic/DMS=truepr=1Q)end=2026-11-12T13:40:00ZQ)last=7d, postgres_endpoints/recreate/DMS=truepr=1Q)end=2026-11-12T13:40:00ZQ)last=7d, postgres_endpoints/add_settings/DMS=pr=1Q)end=2026-11-12T13:40:00ZQ)last=7d, postgres_endpoints/update_autoscaling/DMS=pr=1Q)end=2026-11-12T13:40:00ZQ)last=7d, postgres_databases/update/DMS=pr=1Q)end=2026-11-12T13:40:00ZQ)last=7d, postgres_branches/update_ttl/DMS=truepr=1Q)end=2026-11-12T13:40:00ZQ)last=7d, postgres_projects/purge_on_delete/DMS=truepr=1Q)end=2026-11-12T13:40:00ZQ)last=7d.
Tests
bundle/resources/postgres_projects/create_transient_500injects one 500 on the create POST and one on the operation poll. With the fix, the deploy succeeds after two retries (shown in the output). Without the fix, it fails.bundle/resources/postgres_*acceptance tests and thebundle/direct/...unit tests pass.postgres_projects/basicandpostgres_endpoints/basicon every cloud.This pull request and its description were written by Isaac.