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
There are four assignable [permission levels](https://docs.databricks.com/security/access-control/dlt-acl.html#delta-live-tables-permissions) for [databricks_pipeline](pipeline.md): `CAN_VIEW`, `CAN_RUN`, `CAN_MANAGE`, and `IS_OWNER`. Admins are granted the `CAN_MANAGE` permission by default, and they can assign that permission to non-admin users, and service principals.
217
+
218
+
- The creator of a DLT Pipeline has `IS_OWNER` permission. Destroying `databricks_permissions` resource for a pipeline would revert ownership to the creator.
219
+
- A DLT pipeline must have exactly one owner. If a resource is changed and no owner is specified, the currently authenticated principal would become the new owner of the pipeline. Nothing would change, per se, if the pipeline was created through Terraform.
220
+
- A DLT pipeline cannot have a group as an owner.
221
+
- DLT Pipelines triggered through _Start_ assume the permissions of the pipeline owner and not the user, and service principal who issued Run Now.
222
+
- Read [main documentation](https://docs.databricks.com/security/access-control/dlt-acl.html) for additional detail.
log.Printf("[INFO] Pipeline creation failed, attempting to clean up pipeline %s", id)
131
-
err2:=a.delete(id, timeout)
132
+
err2:=a.Delete(id, timeout)
132
133
iferr2!=nil {
133
134
log.Printf("[WARN] Unable to delete pipeline %s; this resource needs to be manually cleaned up", id)
134
135
return"", fmt.Errorf("multiple errors occurred when creating pipeline. Error while waiting for creation: \"%v\"; error while attempting to clean up failed pipeline: \"%v\"", err, err2)
0 commit comments