-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE] Issue with databricks_sql_permissions
resource
#4140
Comments
databricks_XXX
resourcedatabricks_sql_permissions
resource
The problem here is more on the backend side - I can't create a cluster with such a configuration anymore. Most probably the 1.38 used the cluster created long time ago that was kept for compatibility reasons. |
Due to the internal changes in the backend API, it doesn't allow to create non-UC single-node clusters. Until the fix is implemented on the backend, create a cluster for setting permissions consisting of 1 worker. Also, went through the documentation's grammar. Resolves #4140
Maybe it is related to the permission refactoring done in 1.53? I also have a regression: #4143. |
For posterity, this is a separate issue from |
Current workaround - create a cluster explicitly and provide it's ID as |
will do thankyou |
Configuration
File structure:
main.tf:
variables.tf:
Expected Behavior
Note: the service principal provided in the example is a trivial variable, the issue is that the compute does not initialise, which is the point of the minimum reproducible example.
Should fire up a compute on the workspace to lodge the SQL query like below. This successful execution was carried out with databricks provider 1.38
Actual Behavior
Error output to console and no compute initialised on workspace.
Error: cannot create sql permissions: Access mode LEGACY_SHARED_TABLE_ACL is not compatible with single-node mode. Only NO_ISOLATION and SINGLE_USER are supported.
Steps to Reproduce
Terraform and provider versions
Terraform v1.9.5
on linux_amd64
Is it a regression?
This was working in terraform version 1.38, noticedthe issue when updating to 1.53, and still a bug on 1.54
Debug Output
Important Factoids
No
Would you like to implement a fix?
The text was updated successfully, but these errors were encountered: