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
Copy file name to clipboardExpand all lines: 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
@@ -2,6 +2,7 @@
2
2
3
3
## 0.4.3
4
4
5
+
* Added support for `databricks_permissions` for `databricks_mlflow_experiment` and `databricks_mlflow_model` ([#1013](https://github.com/databrickslabs/terraform-provider-databricks/pull/1013)).
5
6
* Added `Using XXX auth` explanation to HTTP 403 errors, which should help troubleshooting misconfigured authentication or provider aliasing. Example error message now looks like: *cannot create group: /2.0/preview/scim/v2/Groups is only accessible by admins. Using databricks-cli auth: host=https://XXX.cloud.databricks.com/, token=`***REDACTED***`, profile=demo.* All sensitive configuration parameters (`token`, `password`, and `azure_client_secret`) are redacted and replaced with `***REDACTED***` ([#821](https://github.com/databrickslabs/terraform-provider-databricks/issues/821)).
6
7
* Improved documentation with regards to public subnets in AWS quick start ([#1005](https://github.com/databrickslabs/terraform-provider-databricks/pull/1005)).
7
8
* Added `databricks_mount` code genration for [exporter](https://registry.terraform.io/providers/databrickslabs/databricks/latest/docs/guides/experimental-exporter) tooling ([#1006](https://github.com/databrickslabs/terraform-provider-databricks/pull/1006)).
Copy file name to clipboardExpand all lines: docs/resources/mlflow_experiment.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,10 @@ This resource allows you to create MLflow experiments in Databricks.
8
8
## Example Usage
9
9
10
10
```hcl
11
-
resource "databricks_mlflow_experiment" "test" {
12
-
name = "/Users/myuserid/my-experiment"
11
+
data "databricks_current_user" "me" {}
12
+
13
+
resource "databricks_mlflow_experiment" "this" {
14
+
name = "${data.databricks_current_user.me.home}/Sample"
13
15
artifact_location = "dbfs:/tmp/my-experiment"
14
16
description = "My MLflow experiment description"
15
17
}
@@ -22,3 +24,7 @@ The following arguments are supported:
22
24
*`name` - (Required) Name of MLflow experiment. It must be an absolute path within the Databricks workspace, e.g. `/Users/<some-username>/my-experiment`. For more information about changes to experiment naming conventions, see [mlflow docs](https://docs.databricks.com/applications/mlflow/experiments.html#experiment-migration).
23
25
*`artifact_location` - Path to dbfs:/ or s3:// artifact location of the MLflow experiment.
24
26
*`description` - The description of the MLflow experiment.
27
+
28
+
## Access Control
29
+
30
+
*[databricks_permissions](permissions.md#MLflow-Experiment-usage) can control which groups or individual users can *Read*, *Edit*, or *Manage* individual experiments.
*`name` - (Required) Name of MLflow model. Change of name triggers new resource.
32
32
*`description` - The description of the MLflow model.
33
33
*`tags` - Tags for the MLflow model.
34
+
35
+
## Access Control
36
+
37
+
*[databricks_permissions](permissions.md#MLflow-Model-usage) can control which groups or individual users can *Read*, *Edit*, *Manage Staging Versions*, *Manage Production Versions*, and *Manage* individual models.
Valid [permission levels](https://docs.databricks.com/security/access-control/workspace-acl.html#mlflow-experiment-permissions-1) for [databricks_mlflow_experiment](mlflow_experiment.md) are: `CAN_READ`, `CAN_EDIT`, and `CAN_MANAGE`.
336
+
337
+
```hcl
338
+
data "databricks_current_user" "me" {}
339
+
340
+
resource "databricks_mlflow_experiment" "this" {
341
+
name = "${data.databricks_current_user.me.home}/Sample"
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.
0 commit comments