-
Notifications
You must be signed in to change notification settings - Fork 384
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] Changing Pinned status causes cluster restart #379
Comments
I has a fix for that detects when the changes are made in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The change in the pinned status for existing cluster causes the cluster restart because
/clusters/edit
REST API is not idempotent. We need to implement more sophisticated state comparison, and call/clusters/edit
only if actual cluster definition has changed. The cluster restart may also happen if we just add library, etc.Terraform Version
Terraform v0.13.4, Databricks provider is built from Git today
Affected Resource(s)
Environment variable names
Terraform Configuration Files
Initial:
modified:
Debug Output
Debug output: https://gist.github.com/alexott/77d1e43786d6b9981299b6682d0dcfd3
Expected Behavior
Cluster shouldn't be restarted, only pinned status change happens
Actual Behavior
Cluster is restarted, and pinned status changes
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
The text was updated successfully, but these errors were encountered: