Repository navigation
Allow lifecycle.depends_on to target the grants or permissions of a resource - #7435
Merged
Merged
Conversation
Contributor
|
Commit: Regression test reportSelected 2 changed tests (limit=20, 0 not selected) 4 tests: regression=2 unreleased=0 coverage=2 failing=0
TestAccept/bundle/lifecycle/depends-on/DMS=: branch ✅ | main (1e44bb4) ❌ | latest (v1.25.0) ❌main (1e44bb4): latest (v1.25.0): same output as main (1e44bb4) TestAccept/bundle/lifecycle/depends-on/DMS=true: branch ✅ | main (1e44bb4) ❌ | latest (v1.25.0) ❌main (1e44bb4): latest (v1.25.0): same output as main (1e44bb4) |
andrewnester
force-pushed
the
depends-on-grants
branch
2 times, most recently
from
November 10, 2026 08:40
f61a763 to
f0ccb23
Compare
Collaborator
✅ Integration test reportCommit: d03eac9
Top 3 slowest tests (at least 2 minutes):
|
janniklasrose
approved these changes
Nov 10, 2026
denik
reviewed
Nov 10, 2026
denik
reviewed
Nov 10, 2026
…esource lifecycle.depends_on[].resource previously accepted only a resource key (foo or jobs.foo). Users who need a resource to wait for another resource's grants or permissions had no way to express that, so the dependency could only be ordered against the parent resource itself. Accept a qualified key followed by the sub-resource, for example schemas.foo.grants or jobs.foo.permissions. A new Resources.ResolveDependsOn helper maps these references to deployment plan node keys, and both the direct engine and bundle validation use it. A three-segment reference is accepted only when the resource type has a matching grants or permissions sub-resource, otherwise validation reports "no such resource". Co-authored-by: Isaac <no-reply@databricks.com>
andrewnester
force-pushed
the
depends-on-grants
branch
from
November 10, 2026 14:42
bf03149 to
d03eac9
Compare
andrewnester
enabled stacked auto-merge
November 10, 2026 14:44
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Nov 11, 2026
## Release v1.26.0 ### AI Runtime * `air run` reuses its existing workspace connection for config validation instead of opening a second one, which saves a TCP and TLS handshake per submission. ([#7210](#7210)) * Speed up `databricks air run` for git-pinned `code_source` snapshots by compressing the archive in parallel, which substantially shortens packaging on large repositories. ([#7402](#7402)) * Point the `air run -h config` agent-skill hint at the stable `databricks-ai-runtime` skill. ([#7454](#7454)) ### Bundles * Add `DATABRICKS_BUNDLE_INIT_WORKSPACE_HOST_PROFILE`, which names a profile whose host the `workspace_host` template helper returns instead of the selected profile's host. The profile must have the selected profile's workspace ID. ([#7410](#7410)) * Fixed an explicit `false` on optional boolean fields (`variables.*.sensitive`, `artifacts.*.dynamic_version`, `bundle.deployment.lock.force`, `workspace.azure_use_msi`, `replace_existing` on postgres endpoints, databases and roles, and the `experimental.*` flags) being dropped, which hid it from `bundle validate -o json` and kept a target from overriding `true` with it. ([#7412](#7412)) * Stop sending `compute_size` in the app update mask when the bundle does not declare it, so a deploy no longer resets a manually resized app to the default size. ([#7461](#7461)) * `lifecycle.depends_on` can now target the grants or permissions of a resource, as `schemas.foo.grants`. ([#7435](#7435)) * Add support for the `feature_specs` resource type, including UC grants on a feature spec. ([#7364](#7364)) ### Dependency Updates * Update the Go SDK to [v0.197.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.197.0). ([#7457](#7457)) * Bump Go toolchain to 1.27.4. ([#7458](#7458))
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
Allow lifecycle.depends_on to target the grants or permissions of a resource
Why
lifecycle.depends_on[].resource previously accepted only a resource key (foo or jobs.foo). Users who need a resource to wait for another resource's grants or permissions had no way to express that, so the dependency could only be ordered against the parent resource itself.
Accept a qualified key followed by the sub-resource, for example schemas.foo.grants or jobs.foo.permissions. A new
Resources.ResolveDependsOn helper maps these references to deployment plan node keys, and both the direct engine and bundle validation use it. A three-segment reference is accepted only when the resource type has a matching grants or permissions sub-resource, otherwise validation reports "no such resource".
Tests
Added acceptance tests