Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
4aa1187
UC secrets follow a renamed catalog or schema
denik Nov 5, 2026
29326cd
Link PR in changelog fragment
denik Nov 6, 2026
8d4f403
acc: show the skipped schema_id change in the secret parent-rename plans
denik Nov 9, 2026
78c6a60
Point comments at followsParentRename
denik Nov 9, 2026
52e3bf5
direct: let the framework re-key a secret that only follows its paren…
denik Nov 9, 2026
916a787
acc: a secret recreated while its schema is renamed (Badness)
denik Nov 10, 2026
5a229b9
acc: the secret recreated in a renamed schema is deleted where it moved
denik Nov 10, 2026
9125eb6
testserver: report a missing UC secret with UC's message
denik Nov 10, 2026
65958f2
acc: also deploy the secret rename tests from a saved plan (READPLAN)
denik Nov 10, 2026
09d0e81
Make the changelog entry mirror the PR title
denik Nov 16, 2026
ed0a51d
acc: the secret follows the schema's rename in rename_with_model_and_…
denik Nov 16, 2026
7ec06a9
acc: regenerate the secret goldens after rebase
denik Nov 16, 2026
7d79924
direct: drop the DoUpdateWithID check change, which never ran for sec…
denik Nov 17, 2026
fd49352
direct: a secret's own name does not follow a renamed parent (review S1)
denik Nov 17, 2026
81cc9c6
testserver: report a UC secret that already exists with UC's 409 ALRE…
denik Nov 17, 2026
306b7f6
acc: a secret whose schema is renamed out of band is created again (B…
denik Nov 17, 2026
ae7b23c
acc: the secret out-of-band deploy must fail, so use musterr (review)
denik Nov 20, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .nextchanges/bundles/secret-parent-rename.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* UC secrets follow a renamed catalog or schema. ([#7381](https://github.com/databricks/cli/pull/7381))
Original file line number Diff line number Diff line change
Expand Up @@ -9,28 +9,22 @@ Created secrets.secret1
Files: 2 uploaded, 0 deleted
Resources: 3 created, 0 changed, 0 deleted, 0 unchanged

=== Rename the schema. UC moves the model and the secret with it; the model follows the rename, the secret cannot yet, so it is recreated where it moved
=== Rename the schema. UC moves the model and the secret with it, and both follow the rename without a request

>>> update_file.py databricks.yml test-schema- test-schema-renamed-

>>> [CLI] bundle plan
update schemas.schema1
recreate secrets.secret1

Plan: 1 to add, 1 to change, 1 to delete, 1 unchanged
Plan: 0 to add, 1 to change, 0 to delete, 2 unchanged

>>> [CLI] bundle deploy --auto-approve
Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle-[UNIQUE_NAME]/default/files...
Recreated secrets.secret1
Updated schemas.schema1
Files: 2 uploaded, 0 deleted
Resources: 1 created, 1 changed, 1 deleted, 1 unchanged
Resources: 0 created, 1 changed, 0 deleted, 2 unchanged

>>> print_requests.py --sort //unity-catalog
{
"method": "DELETE",
"path": "/api/2.1/unity-catalog/secrets/main.test-schema-renamed-[UNIQUE_NAME].mysecret"
}
{
"method": "PATCH",
"path": "/api/2.1/unity-catalog/schemas/main.test-schema-[UNIQUE_NAME]",
Expand All @@ -40,16 +34,6 @@ Resources: 1 created, 1 changed, 1 deleted, 1 unchanged
"new_name": "test-schema-renamed-[UNIQUE_NAME]"
}
}
{
"method": "POST",
"path": "/api/2.1/unity-catalog/secrets",
"body": {
"catalog_name": "main",
"name": "mysecret",
"schema_name": "test-schema-renamed-[UNIQUE_NAME]",
"value": "secret-value"
}
}

>>> [CLI] registered-models get main.test-schema-renamed-[UNIQUE_NAME].mymodel
{
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ title "Deploy a schema with a registered model and a secret in it"
trace $CLI bundle deploy
print_requests.py //unity-catalog &> LOG.deploy_requests

title "Rename the schema. UC moves the model and the secret with it; the model follows the rename, the secret cannot yet, so it is recreated where it moved"
title "Rename the schema. UC moves the model and the secret with it, and both follow the rename without a request"
trace update_file.py databricks.yml test-schema- test-schema-renamed-
trace $CLI bundle plan
trace $CLI bundle deploy --auto-approve
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
bundle:
name: test-bundle-$UNIQUE_NAME

variables:
secret_value:
description: The secret's value

resources:
catalogs:
catalog1:
name: test_catalog_$UNIQUE_NAME
schemas:
schema1:
catalog_name: ${resources.catalogs.catalog1.name}
name: myschema
secrets:
secret1:
catalog_name: ${resources.catalogs.catalog1.name}
schema_name: ${resources.schemas.schema1.name}
name: mysecret
value: ${var.secret_value}
comment: c1
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
Cloud = true
EnvMatrix.DMS = ["", "true"]
EnvMatrix.READPLAN = ["", "1"]
Loading
Loading