Skip to content

Commit

Permalink
update to use application_id as privilege for SP
Browse files Browse the repository at this point in the history
  • Loading branch information
leedabee authored May 25, 2022
1 parent 0647db0 commit a5a14d2
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/resources/sql_permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ The following arguments are available to specify the data object you need to enf

You must specify one or many `privilege_assignments` configuration blocks to declare `privileges` to a `principal`, which corresponds to `display_name` of [databricks_group](group.md#display_name) or [databricks_user](user.md#display_name). Terraform would ensure that only those principals and privileges defined in the resource are applied for the data object and would remove anything else. It would not remove any transitive privileges. `DENY` statements are intentionally not supported. Every `privilege_assignments` has the following required arguments:

* `principal` - `display_name` of [databricks_group](group.md#display_name) or [databricks_user](user.md#display_name).
* `principal` - `display_name` for a [databricks_group](group.md#display_name) or [databricks_user](user.md#display_name) | `application_id` for a [service_principal](service_principal.md)
* `privileges` - set of available privilege names in upper case.

[Available](https://docs.databricks.com/security/access-control/table-acls/object-privileges.html) privilege names are:
Expand Down

0 comments on commit a5a14d2

Please sign in to comment.