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
Added databricks_model_serving support to databricks_permissions (#2331)
* Add model serving support to `databricks_permissions`
To support permissions assignment we also need to expose a new attribute with internal ID
of the model serving endpoint.
* Update docs/resources/model_serving.md
Co-authored-by: Arpit Jasapara <[email protected]>
* Update docs/resources/model_serving.md
Co-authored-by: Arpit Jasapara <[email protected]>
---------
Co-authored-by: Arpit Jasapara <[email protected]>
Copy file name to clipboardExpand all lines: docs/resources/model_serving.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,17 @@ The following arguments are supported:
68
68
*`served_model_name` - (Required) The name of the served model this route configures traffic for. This needs to match the name of a `served_models` block
69
69
*`traffic_percentage` - (Required) The percentage of endpoint traffic to send to this route. It must be an integer between 0 and 100 inclusive.
70
70
71
+
## Attribute Reference
72
+
73
+
In addition to all arguments above, the following attributes are exported:
74
+
75
+
*`id` - Equal to the `name` argument and used to identify the serving endpoint.
76
+
*`serving_endpoint_id` - Unique identifier of the serving endpoint primarily used to set permissions and refer to this instance for other operations.
77
+
78
+
## Access Control
79
+
80
+
*[databricks_permissions](permissions.md#model-serving-usage) can control which groups or individual users can *Manage*, *Query* or *View* individual serving endpoints.
81
+
71
82
## Timeouts
72
83
73
84
The `timeouts` block allows you to specify `create` and `update` timeouts. The default right now is 45 minutes for both operations.
By default on AWS deployments, all admin users can sign in to Databricks using either SSO or their username and password, and all API users can authenticate to the Databricks REST APIs using their username and password. As an admin, you [can limit](https://docs.databricks.com/administration-guide/users-groups/single-sign-on/index.html#optional-configure-password-access-control) admin users’ and API users’ ability to authenticate with their username and password by configuring `CAN_USE` permissions using password access control.
@@ -734,6 +780,7 @@ Exactly one of the following arguments is required:
734
780
-`repo_path` - path of databricks repo directory(`/Repos/<username>/...`)
735
781
-`experiment_id` - [MLflow experiment](mlflow_experiment.md) id
736
782
-`registered_model_id` - [MLflow registered model](mlflow_model.md) id
-`authorization` - either [`tokens`](https://docs.databricks.com/administration-guide/access-control/tokens.html) or [`passwords`](https://docs.databricks.com/administration-guide/users-groups/single-sign-on/index.html#configure-password-permission).
738
785
-`sql_endpoint_id` - [SQL warehouse](sql_endpoint.md) id
739
786
-`sql_dashboard_id` - [SQL dashboard](sql_dashboard.md) id
0 commit comments