Added databricks_permission resource for managing permissions for individual principals.
          #5161
        
          
      
      
        
          +2,137
        
        
          −34
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
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:Caveat: Since we cannot remove an individual permission, the
Deleteoperation is performed asRead/Put, so we need to use a lock around each object.Tests
make testrun locallydocs/folderinternal/acceptanceNEXT_CHANGELOG.mdfile