You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document new fields in databricks_model_serving and deprecate invalid_keywords and valid_topics in AI Gateway configuration (#4851)
## Changes
<!-- Summary of your changes that are easy to understand -->
Should be merged after #4844
## Tests
<!--
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->
- [x] `make test` run locally
- [x] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] using Go SDK
- [ ] using TF Plugin Framework
- [x] has entry in `NEXT_CHANGELOG.md` file
Copy file name to clipboardExpand all lines: NEXT_CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@
10
10
* Use single-node cluster for `databricks_sql_permissions` ([#4813](https://github.com/databricks/terraform-provider-databricks/pull/4813)).
11
11
* Allow to retrieve service principal data by SCIM ID ([#3142](https://github.com/databricks/terraform-provider-databricks/pull/3142)).
12
12
* Add support for Lakebase `databricks_database_instance` in `databricks_permissions` ([#4824](https://github.com/databricks/terraform-provider-databricks/pull/4824)).
13
+
* Document new fields in `databricks_model_serving` and deprecate `invalid_keywords` and `valid_topics` in AI Gateway configuration ([#4851](https://github.com/databricks/terraform-provider-databricks/pull/4851)).
13
14
* Added support for Alert V2 in `databricks_permissions` ([#4831](https://github.com/databricks/terraform-provider-databricks/pull/4831)).
14
15
* Replace instead of dropping Delta `databricks_sql_table` ([#2424](https://github.com/databricks/terraform-provider-databricks/pull/2424)).
15
16
* Added `clean_rooms_clean_room` resource and data sources ([#4844](https://github.com/databricks/terraform-provider-databricks/pull/4844)).
Copy file name to clipboardExpand all lines: docs/resources/model_serving.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,7 @@ The following arguments are supported:
132
132
*`ai_gateway` - (Optional) A block with AI Gateway configuration for the serving endpoint. *Note: only external model endpoints are supported as of now.*
133
133
*`route_optimized` - (Optional) A boolean enabling route optimization for the endpoint. *Note: only available for custom models.*
134
134
*`budget_policy_id` - (Optiona) The Budget Policy ID set for this serving endpoint.
135
+
*`description` - (Optional) The description of the model serving endpoint.
135
136
136
137
### served_entities Configuration Block
137
138
@@ -237,7 +238,8 @@ The following arguments are supported:
237
238
### rate_limits Configuration Block
238
239
239
240
*`calls` - (Required) Used to specify how many calls are allowed for a key within the renewal_period.
240
-
*`key` - (Optional) Key field for a serving endpoint rate limit. Currently, only `user` and `endpoint` are supported, with `endpoint` being the default if not specified.
241
+
*`key` - (Optional) Key field for a serving endpoint rate limit. Currently, `user`, `user_group`, `service_principal`, and `endpoint` are supported, with `endpoint` being the default if not specified.
242
+
*`principal` - (Optional) Principal field for a user, user group, or service principal to apply rate limiting to. Accepts a user email, group name, or service principal application ID.
241
243
*`renewal_period` - (Required) Renewal period field for a serving endpoint rate limit. Currently, only `minute` is supported.
242
244
243
245
### ai_gateway Configuration Block
@@ -246,8 +248,8 @@ The following arguments are supported:
246
248
*`enabled` - Whether to enable traffic fallback. When a served entity in the serving endpoint returns specific error codes (e.g. 500), the request will automatically be round-robin attempted with other served entities in the same endpoint, following the order of served entity list, until a successful response is returned.
247
249
*`guardrails` - (Optional) Block with configuration for AI Guardrails to prevent unwanted data and unsafe data in requests and responses. Consists of the following attributes:
248
250
*`input` - A block with configuration for input guardrail filters:
249
-
*`invalid_keywords` - List of invalid keywords. AI guardrail uses keyword or string matching to decide if the keyword exists in the request or response content.
250
-
*`valid_topics` - The list of allowed topics. Given a chat request, this guardrail flags the request if its topic is not in the allowed topics.
251
+
*`invalid_keywords` - (Deprecated) List of invalid keywords. AI guardrail uses keyword or string matching to decide if the keyword exists in the request or response content.
252
+
*`valid_topics` - (Deprecated) The list of allowed topics. Given a chat request, this guardrail flags the request if its topic is not in the allowed topics.
251
253
*`safety` - the boolean flag that indicates whether the safety filter is enabled.
252
254
*`pii` - Block with configuration for guardrail PII filter:
253
255
*`behavior` - a string that describes the behavior for PII filter. Currently only `BLOCK` value is supported.
0 commit comments