Use VectorSearchEndpointPermissionLevel for VS endpoint permissions - #6022
Merged
Conversation
The SDK exposes a dedicated permission level type for vector search endpoints; switch VectorSearchEndpoint.Permissions to use it via the PermissionT[L] generic, matching the typing already in place for jobs, apps, model serving, etc. Regenerated jsonschema.json and added the annotations placeholder for the new VectorSearchEndpointPermission. Co-authored-by: Isaac
janniklasrose
marked this pull request as ready for review
July 22, 2026 11:28
janniklasrose
enabled auto-merge
July 22, 2026 11:28
Collaborator
Integration test reportCommit: 9799179
8 interesting tests: 4 RECOVERED, 4 SKIP
Top 6 slowest tests (at least 2 minutes):
|
denik
approved these changes
Jul 29, 2026
Collaborator
Integration test reportCommit: a32f465
444 interesting tests: 436 FAIL, 4 RECOVERED, 2 KNOWN, 2 SKIP
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Jul 29, 2026
## Release v1.10.0 ### CLI * `ssh connect` now supports specifying a serverless usage policy with `--usage-policy-id` ### Bundles * Fixed `bundle deploy`/`bundle destroy` failing when an app enters the transient DELETING state between plan and apply (e.g. with a saved plan); the delete is now treated as complete instead of erroring (direct engine only). * Fixed `bundle deploy`/`bundle destroy` failing when an app is still in the transient DELETING state; the delete is now treated as complete instead of erroring (direct engine only). * `bundle destroy --force-lock` now proceeds without a deployment lock when the workspace directory is at its child-node limit and cannot accept the lock file, so a deployment can still be torn down when the workspace is full. * Empty-string values on optional (omitempty) resource fields are now dropped before deployment instead of being sent to the backend. This fixes deploys failing with errors like `'' is not a valid cluster policy ID` when a field such as `policy_id` was set to `""` (often via a variable that resolved to an empty string). The behavior now matches between the terraform and direct engines and is reflected in `bundle validate -o json`. * `bundle validate` and `bundle deploy` now reject a grant that is missing a `principal` with an error instead of a warning. Previously the deploy would start and, on the direct engine, create the securable before the grants PATCH failed (`400 INVALID_PARAMETER_VALUE`), leaving a partially-applied deployment. * `bundle validate` and `bundle deploy` now reject a grant with an empty `privileges` list with an error. Previously, on the direct engine, such a grant never converged: the backend drops principals with no privileges, so every subsequent `bundle plan` reported the grant as a perpetual update. * Fixes [#6030](#6030): spurious `update` on catalog/schema/volume grants (direct engine); a principal granted `ALL_PRIVILEGES` no longer drifts when the backend also reports the concrete privileges it implies ([#6064](#6064)). * Use vector search endpoint permission types that are supported by the backend ([#6022](#6022)). ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.160.0 to v0.165.0. * Upgrade Terraform provider to 1.123.0
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
The SDK exposes a dedicated permission level type for vector search endpoints; switch
VectorSearchEndpoint.Permissionsto use it via thePermissionT[L]generic, matching the typing already in place for jobs, apps, model serving, etc. Regenerated jsonschema.json and added the annotations placeholder for the new VectorSearchEndpointPermission.Why
Allows DAB-side validation of types in the schema instead of backend erroring on unsupported permissions