Skip to content

Re-key grants when their parent's ID changes - #7345

Merged
denik merged 8 commits into
mainfrom
denik/grants-rekey
Nov 4, 2026
Merged

Re-key grants when their parent's ID changes#7345
denik merged 8 commits into
mainfrom
denik/grants-rekey

Conversation

@denik

@denik denik commented Nov 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Changes

Grants are keyed by their parent's full name (volume/main.s.vol). When the parent got a new ID, the grants were applied under the new name, but their state kept the old ID. This happens on a rename (catalogs, volumes) or a recreate under a new name (schemas). The next bundle plan then proposed the grants again. On UC the old name 404s, so the plan shows create ...grants once; on the test server the plan shows update ...grants forever.

full_name is now an updatable_id_fields entry for every grants type, and DoUpdateWithID records the new ID. This follows secret_scopes.permissions.yml, which solves the same problem for secret scope ACLs. The rule lives in a single configs/grants.yml: a config file named after a sub-resource now applies to that sub-resource of every parent (catalogs.grants, schemas.grants, ...).

Needed before #7343 (schema rename), so that renamed schemas keep their grants in sync.

Tests

New acceptance tests, Cloud = true, passing locally and on AWS:

  • grants/volume_change_name: volume rename (update_id).
  • grants/schemas/change_name: schema name change (a recreate today).

The first commit adds them with the pre-fix goldens; the second commit shows the fix flipping them to a no-op plan.

This pull request and its description were written by Isaac.

denik and others added 2 commits November 4, 2026 13:55
@denik Isaac
acc: grants keep a stale ID after their parent's ID changes
48e7200 
Co-authored-by: Isaac <no-reply@databricks.com>
@denik Isaac
Re-key grants when their parent's ID changes
3c00e07 
The grants ID embeds the parent's full name. When the parent was renamed
(catalogs, volumes) or recreated under a new name (schemas), the grants were
applied to the new name but their state kept the old ID, so the next plan
proposed them again: UC 404s on the old name (plan: create), the test server
does not (plan: update, forever).

full_name is now an updatable ID field of every grants type, and
DoUpdateWithID records the new ID.

Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions github-actions Bot added the DABs DABs related issues label Nov 4, 2026
@denik Isaac
Link PR in changelog fragment
e96fe76 
Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions

github-actions Bot commented Nov 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Commit: ecf3adaff | Workflow run

Regression test report

Selected 2 changed tests (limit=20, 0 not selected)

4 tests: regression=4 unreleased=0 coverage=0 failing=0
test branch main (ef99113) latest (v1.24.0)
TestAccept/bundle/resources/grants/schemas/change_name/DMS= ✅ ❌ ❌
TestAccept/bundle/resources/grants/schemas/change_name/DMS=true ✅ ❌ ❌
TestAccept/bundle/resources/grants/volume_change_name/DMS= ✅ ❌ ❌
TestAccept/bundle/resources/grants/volume_change_name/DMS=true ✅ ❌ ❌
TestAccept/bundle/resources/grants/schemas/change_name/DMS=: branch ✅ | main (ef99113) ❌ | latest (v1.24.0) ❌

main (ef99113):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/schemas/change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsschemaschange_nameDMS=3769790890/002/output.txt
        @@ -43,8 +43,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME]",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME]"
        @@ -106,11 +105,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py schemas schema1.grants id
        -schemas schema1.grants id='schema/main.test-schema-renamed-[UNIQUE_NAME]'
        +schemas schema1.grants id='schema/main.test-schema-[UNIQUE_NAME]'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
        +update schemas.schema1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 1 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-renamed-4iliezzjv5hidkvzqoyoz6krki",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }

latest (v1.24.0):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/schemas/change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsschemaschange_nameDMS=192986567/002/output.txt
        @@ -43,8 +43,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME]",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME]"
        @@ -106,11 +105,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py schemas schema1.grants id
        -schemas schema1.grants id='schema/main.test-schema-renamed-[UNIQUE_NAME]'
        +schemas schema1.grants id='schema/main.test-schema-[UNIQUE_NAME]'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
        +update schemas.schema1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 1 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-renamed-fcxc7nnd2rdv5f5kvb76toot6a",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }
TestAccept/bundle/resources/grants/schemas/change_name/DMS=true: branch ✅ | main (ef99113) ❌ | latest (v1.24.0) ❌

main (ef99113):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/schemas/change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsschemaschange_nameDMS=true372179663/002/output.txt
        @@ -43,8 +43,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME]",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME]"
        @@ -106,11 +105,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py schemas schema1.grants id
        -schemas schema1.grants id='schema/main.test-schema-renamed-[UNIQUE_NAME]'
        +schemas schema1.grants id='schema/main.test-schema-[UNIQUE_NAME]'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
        +update schemas.schema1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 1 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-renamed-os4n33pwive4rp3pkuzb2qla4m",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }

latest (v1.24.0):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/schemas/change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsschemaschange_nameDMS=true3778275564/002/output.txt
        @@ -43,8 +43,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME]",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME]"
        @@ -106,11 +105,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py schemas schema1.grants id
        -schemas schema1.grants id='schema/main.test-schema-renamed-[UNIQUE_NAME]'
        +schemas schema1.grants id='schema/main.test-schema-[UNIQUE_NAME]'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
        +update schemas.schema1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 1 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-renamed-qmgfnsntkjh7dnsmyk5ci7gpim",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }
FAIL
TestAccept/bundle/resources/grants/volume_change_name/DMS=: branch ✅ | main (ef99113) ❌ | latest (v1.24.0) ❌

main (ef99113):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/volume_change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsvolume_change_nameDMS=814414104/002/output.txt
        @@ -54,8 +54,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME].myvolume",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME].myvolume"
        @@ -107,11 +106,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py volumes volume1.grants id
        -volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume_renamed'
        +volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 3 unchanged
        +update volumes.volume1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 2 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/volumes/main.test-schema-4rgklwvscvamhnzt5ghsemcdwu.myvolume_renamed"
        LOG.destroy_requests: }
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-4rgklwvscvamhnzt5ghsemcdwu",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }

latest (v1.24.0):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/volume_change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsvolume_change_nameDMS=65687098/002/output.txt
        @@ -54,8 +54,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME].myvolume",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME].myvolume"
        @@ -107,11 +106,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py volumes volume1.grants id
        -volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume_renamed'
        +volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 3 unchanged
        +update volumes.volume1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 2 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/volumes/main.test-schema-fgj24qffkjdtdatgkkgymc4ucu.myvolume_renamed"
        LOG.destroy_requests: }
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-fgj24qffkjdtdatgkkgymc4ucu",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }
TestAccept/bundle/resources/grants/volume_change_name/DMS=true: branch ✅ | main (ef99113) ❌ | latest (v1.24.0) ❌

main (ef99113):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/volume_change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsvolume_change_nameDMS=true2133466883/002/output.txt
        @@ -54,8 +54,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME].myvolume",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME].myvolume"
        @@ -107,11 +106,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py volumes volume1.grants id
        -volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume_renamed'
        +volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 3 unchanged
        +update volumes.volume1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 2 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/volumes/main.test-schema-w26f3abph5fgjav5aw3v5il5u4.myvolume_renamed"
        LOG.destroy_requests: }
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-w26f3abph5fgjav5aw3v5il5u4",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }
FAIL

latest (v1.24.0):

acceptance_test.go:1342: Diff:
        --- bundle/resources/grants/volume_change_name/output.txt
        +++ /tmp/TestAcceptbundleresourcesgrantsvolume_change_nameDMS=true2188130323/002/output.txt
        @@ -54,8 +54,7 @@
         >>> [CLI] bundle plan --output json
         {
           "full_name": {
        -    "action": "update_id",
        -    "reason": "id_changes",
        +    "action": "update",
             "old": "main.test-schema-[UNIQUE_NAME].myvolume",
             "new": "",
             "remote": "main.test-schema-[UNIQUE_NAME].myvolume"
        @@ -107,11 +106,13 @@
         
         === The grants are recorded under the new name, so the next plan is a no-op
         >>> read_state.py volumes volume1.grants id
        -volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume_renamed'
        +volumes volume1.grants id='volume/main.test-schema-[UNIQUE_NAME].myvolume'
         
         >>> [CLI] bundle plan
        -Plan: 0 to add, 0 to change, 0 to delete, 3 unchanged
        +update volumes.volume1.grants
         
        +Plan: 0 to add, 1 to change, 0 to delete, 2 unchanged
        +
         >>> [CLI] bundle destroy --auto-approve
         The following resources will be deleted:
           delete resources.schemas.schema1
        
    acceptance_test.go:1120: 
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/volumes/main.test-schema-znhjk3vf5bci5ormmqtvxasmbi.myvolume_renamed"
        LOG.destroy_requests: }
        LOG.destroy_requests: {
        LOG.destroy_requests:   "method": "DELETE",
        LOG.destroy_requests:   "path": "/api/2.1/unity-catalog/schemas/main.test-schema-znhjk3vf5bci5ormmqtvxasmbi",
        LOG.destroy_requests:   "q": {
        LOG.destroy_requests:     "force": "true"
        LOG.destroy_requests:   }
        LOG.destroy_requests: }

@denik
denik added this pull request to stack #7346 November 4, 2026 13:16
@denik denik mentioned this pull request Nov 4, 2026
Open
@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: ecf3ada

Run: 41853032938

Env ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 277 15 5:38
✅​ aws-windows-latest-4core-16gb 279 13 4:39
✅​ azure linux-2core-8gb 276 15 5:41
✅​ azure-windows-latest-4core-16gb 278 13 4:29
✅​ gcp linux-2core-8gb 277 15 6:17
✅​ gcp-windows-latest-4core-16gb 279 13 4:42
Top 3 slowest tests (at least 2 minutes):
duration env testname
3:33 gcp-windows-latest-4core-16gb TestAccept
3:28 azure-windows-latest-4core-16gb TestAccept
3:16 aws-windows-latest-4core-16gb TestAccept

@denik Isaac
Use a single grants.yml for every grants type
dbd7fd0 
A config file named after a sub-resource now applies to that sub-resource of
every parent, so the ten identical <parent>.grants.yml files become one.

Co-authored-by: Isaac <no-reply@databricks.com>
@denik
denik marked this pull request as ready for review November 4, 2026 14:43
@denik
denik requested review from a team as code owners November 4, 2026 14:43
@denik Isaac
Drop engine mention from changelog entry
28a92ca 
Co-authored-by: Isaac <no-reply@databricks.com>
@denik
denik enabled stacked auto-merge November 4, 2026 14:46
denik and others added 3 commits November 4, 2026 15:49
@denik Isaac
acc: trace read_state.py in the grants change_name tests
7a3df00 
Co-authored-by: Isaac <no-reply@databricks.com>
@denik Isaac
acc: drop text plan where the JSON plan already shows it
6274fc1 
Co-authored-by: Isaac <no-reply@databricks.com>
@denik Isaac
acc: show only the grants plan entry's changes
ecf3ada 
Co-authored-by: Isaac <no-reply@databricks.com>
@denik
denik added this pull request to the merge queue Nov 4, 2026
Merged via the queue into main with commit e1b8c92 Nov 4, 2026
28 checks passed
@denik
denik deleted the denik/grants-rekey branch November 4, 2026 15:33
@denik denik mentioned this pull request Nov 4, 2026
Merged
@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: e1b8c92

Run: 41859137575

Env ❌​FAIL 🔄​flaky ✅​pass 🙈​skip Time
🔄​ aws linux-2core-8gb 8 1509 1255 312:21
❌​ aws-windows-latest-4core-16gb 21 1415 1282 254:02
✅​ azure linux-2core-8gb 1364 1307 136:45
✅​ azure-windows-latest-4core-16gb 1283 1334 141:48
🔄​ gcp linux-2core-8gb 2 1349 1312 156:01
🔄​ gcp-windows-latest-4core-16gb 2 1268 1339 161:49
26 interesting tests: 21 FAIL, 5 flaky
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
❌​ TestAccept ✅​p ❌​F ✅​p ✅​p
🔄​ TestAccept/bundle/debug/fetch-repository-info/DMS= ✅​p ✅​p 🔄​f 🔄​f
🔄​ TestAccept/bundle/debug/fetch-repository-info/DMS=true ✅​p ✅​p 🔄​f 🔄​f
❌​ TestAccept/bundle/deploy/spark-jar-task ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/deploy/spark-jar-task/DMS= 🔄​f ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/deploy/spark-jar-task/DMS=true 🔄​f ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN= ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1 ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN= ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1 ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1 ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1 ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/deploy/update-after-create ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/deploy/update-after-create/DMS= ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/lifecycle-started ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/lifecycle-started-toggle ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS= 🔄​f ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true 🔄​f ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true ✅​p ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/resize-terminated-fallback 🔄​f ❌​F ✅​p ✅​p
🔄​ TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS= 🔄​f ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=true ✅​p ❌​F ✅​p ✅​p
🔄​ TestAccept/bundle/resources/postgres_synced_tables/recreate 🔄​f ✅​p 🙈​s 🙈​s
🔄​ TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS=true 🔄​f ✅​p
Top 50 slowest tests (at least 2 minutes):
duration env testname
30:26 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
23:01 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=
22:54 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
18:44 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
17:22 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
16:29 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
14:51 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
14:50 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
13:35 aws linux-2core-8gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=true
10:56 aws linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/update-after-create/DMS=
9:28 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:12 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:08 azure linux-2core-8gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=
9:02 aws linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=
8:58 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:49 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:44 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:41 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:35 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/update-after-create/DMS=true
8:25 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:19 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
8:13 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:08 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
8:08 aws-windows-latest-4core-16gb TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=
7:44 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:41 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
7:33 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:32 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
7:19 aws linux-2core-8gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1
7:17 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:13 aws linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/update-after-create/DMS=true
7:09 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
7:06 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/simple/DMS=true
7:06 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:03 aws linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/simple/DMS=
6:53 aws-windows-latest-4core-16gb TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=
6:50 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
6:40 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:40 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/simple/DMS=
6:39 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:33 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:21 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:17 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=
6:08 aws linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
5:49 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:48 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:45 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:42 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=
5:38 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
5:36 aws linux-2core-8gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@andrewnester andrewnester andrewnester approved these changes
@rclarey rclarey Awaiting requested review from rclarey rclarey is a code owner automatically assigned from databricks/eng-deco-cli
@Sankalp-Mittal Sankalp-Mittal Awaiting requested review from Sankalp-Mittal Sankalp-Mittal is a code owner automatically assigned from databricks/eng-deco-dabs

Assignees

No one assigned

Labels

DABs DABs related issues

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@denik @eng-dev-ecosystem-bot @andrewnester