Skip to content

Conversation

@alexott
Copy link
Contributor

@alexott alexott commented Oct 29, 2025

Changes

This resource provides fine-grained control over permissions by managing a single principal's access to a single object, unlike databricks_permissions, which manages all principals' access to an object at once. This is particularly useful for:

  • Managing permissions for different teams independently
  • Token and password authorization permissions that previously required all principals in one resource
  • Avoiding conflicts when multiple configurations manage different principals on the same object

Caveat: Since we cannot remove an individual permission, the Delete operation is performed as Read/Put, so we need to use a lock around each object.

Tests

  • make test run locally
  • tested manually
  • relevant change in docs/ folder
  • covered with integration tests in internal/acceptance
  • using Go SDK
  • using TF Plugin Framework
  • has entry in NEXT_CHANGELOG.md file

…ndividual principals.

This resource provides fine-grained control over permissions by managing a single
principal's access to a single object, unlike `databricks_permissions` which manages all
principals' access to an object at once. This is particularly useful for:

- Managing permissions for different teams independently
- Token and password authorization permissions that previously required all principals in one resource
- Avoiding conflicts when multiple configurations manage different principals on the same object
@alexott alexott requested review from a team as code owners October 29, 2025 10:15
@alexott alexott requested review from mgyucht and removed request for a team October 29, 2025 10:15
@alexott alexott temporarily deployed to test-trigger-is October 29, 2025 10:15 — with GitHub Actions Inactive
@alexott alexott temporarily deployed to test-trigger-is October 29, 2025 10:16 — with GitHub Actions Inactive
@alexott alexott temporarily deployed to test-trigger-is October 29, 2025 14:56 — with GitHub Actions Inactive
@github-actions
Copy link

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/terraform

Inputs:

  • PR number: 5161
  • Commit SHA: ac8512437e45348331af3eba1dea3f520b26fe36

Checks will be approved automatically on success.

@alexott alexott temporarily deployed to test-trigger-is October 29, 2025 14:57 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants