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
[Doc] Document management of permissions of databricks_budget_policy resource (#4561)
## Changes
<!-- Summary of your changes that are easy to understand -->
Resolves#4555
## Tests
<!--
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->
- [x] relevant change in `docs/` folder
Copy file name to clipboardExpand all lines: NEXT_CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@
8
8
9
9
### Documentation
10
10
11
+
* Document management of permissions of `databricks_budget_policy` resource ([#4561](https://github.com/databricks/terraform-provider-databricks/pull/4561))
*`name` - (Required) Unique identifier of a rule set. The name determines the resource to which the rule set applies. Currently, only default rule sets are supported. The following rule set formats are supported:
*`grant_rules` - (Required) The access control rules to be granted by this rule set, consisting of a set of principals and roles to be granted to them.
223
268
@@ -238,11 +283,13 @@ grant_rules {
238
283
239
284
Arguments of the `grant_rules` block are:
240
285
241
-
*`role` - (Required) Role to be granted. The supported roles are listed below. For more information about these roles, refer to [service principal roles](https://docs.databricks.com/security/auth-authz/access-control/service-principal-acl.html#service-principal-roles), [group roles](https://docs.databricks.com/en/administration-guide/users-groups/groups.html#manage-roles-on-an-account-group-using-the-workspace-admin-settings-page) or [marketplace roles](https://docs.databricks.com/en/marketplace/get-started-provider.html#assign-the-marketplace-admin-role).
286
+
*`role` - (Required) Role to be granted. The supported roles are listed below. For more information about these roles, refer to [service principal roles](https://docs.databricks.com/security/auth-authz/access-control/service-principal-acl.html#service-principal-roles), [group roles](https://docs.databricks.com/en/administration-guide/users-groups/groups.html#manage-roles-on-an-account-group-using-the-workspace-admin-settings-page), [marketplace roles](https://docs.databricks.com/en/marketplace/get-started-provider.html#assign-the-marketplace-admin-role) or [budget policy permissions](https://docs.databricks.com/aws/en/admin/usage/budget-policies#manage-budget-policy-permissions).
242
287
*`roles/servicePrincipal.manager` - Manager of a service principal.
243
288
*`roles/servicePrincipal.user` - User of a service principal.
244
289
*`roles/group.manager` - Manager of a group.
245
290
*`roles/marketplace.admin` - Admin of marketplace.
291
+
*`roles/budgetPolicy.manager` - Manager of a budget policy.
292
+
*`roles/budgetPolicy.user` - User of a budget policy.
246
293
*`principals` - (Required) a list of principals who are granted a role. The following format is supported:
247
294
*`users/{username}` (also exposed as `acl_principal_id` attribute of `databricks_user` resource).
248
295
*`groups/{groupname}` (also exposed as `acl_principal_id` attribute of `databricks_group` resource).
Copy file name to clipboardExpand all lines: docs/resources/budget_policy.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ subcategory: "FinOps"
5
5
6
6
Administrators can use budget policies to ensure that the correct tags appear automatically on serverless resources without depending on users to attach tags manually, allowing for customized cost reporting and chargebacks. Budget policies consist of tags that are applied to any serverless compute activity incurred by a user assigned to the policy. The tags are logged in your billing records, allowing you to attribute serverless usage to specific budgets.
7
7
8
-
-> **Note**This resource can only be used with an account-level provider!
8
+
-> This resource can only be used with an account-level provider!
*`policy_name` - (Required) The name of the policy. Must be unique among active policies. Can contain only characters from the ISO 8859-1 (latin1) set.
27
28
*`custom_tags` - (Optional) A list of tags defined by the customer. At most 20 entries are allowed per policy.
28
29
29
30
### custom_tags Configuration Block
31
+
30
32
*`key` - The key of the tag. - Must be unique among all custom tags of the same policy. Cannot be “budget-policy-name”, “budget-policy-id” or "budget-policy-resolution-result" as these tags are preserved.
31
33
*`value` - The value of the tag.
32
34
33
-
34
35
## Attribute Reference
35
36
36
37
In addition to all arguments above, the following attribute is exported:
38
+
37
39
*`policy_id` - ID of the budget policy
38
40
41
+
## Access Control
42
+
43
+
*[databricks_access_control_rule_set](access_control_rule_set.md) can control which groups or individual users can manage or use the given budget policy.
0 commit comments