Skip to content

Commit

Permalink
[Doc] Add a warning that attribute should be used in `databricks_perm…
Browse files Browse the repository at this point in the history
…issions` for `databricks_vector_search_endpoint` (#4312)

## Changes
<!-- Summary of your changes that are easy to understand -->

Resolves #4311

## Tests
<!-- 
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->

- [ ] `make test` run locally
- [x] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] relevant acceptance tests are passing
- [ ] using Go SDK
  • Loading branch information
alexott authored Dec 12, 2024
1 parent 4697aa3 commit 964e868
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/resources/permissions.md
Original file line number Diff line number Diff line change
@@ -643,6 +643,8 @@ resource "databricks_permissions" "ml_serving_usage" {

Valid permission levels for [databricks_vector_search_endpoint](vector_search_endpoint.md) are: `CAN_USE` and `CAN_MANAGE`.

-> You need to use the `endpoint_id` attribute of `databricks_vector_search_endpoint` as value for `vector_search_endpoint_id`, not the `id`!

```hcl
resource "databricks_vector_search_endpoint" "this" {
name = "vector-search-test"

0 comments on commit 964e868

Please sign in to comment.