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
[Internal] Use SDKv2 Implementation for databricks_share resource as default (#4931)
## Changes
<!-- Summary of your changes that are easy to understand -->
This PR:
- reverts
#4846.
- Adds a note under breaking changes to highlight the issue.
- Move the next release to patch.
**Context**
databricks_share resource exists in 2 implementations SDKv2 and Plugin
framework. In
#4846,
plugin framework implementation (`databricks_share_pluginframework`) was
made default (`databricks_share`) but this lead to surfacing an
underlying issue in plugin framework implementation leading to panic:
#4913
```
Stack trace from the terraform-provider-databricks_v1.86.0 plugin:
panic: runtime error: index out of range [0] with length 0
goroutine 68 [running]:
github.com/databricks/terraform-provider-databricks/internal/providers/pluginfw/products/sharing.(*ShareResource).syncEffectiveFields(_, {_, _}, {{{0x2, {0xc0007f6b40, 0x22}}, {0x2, 0x196f67034f0}, {0x2, {0xc0007f6b70, ...}}, ...}}, ...)
/home/runner/work/terraform-provider-databricks/terraform-provider-databricks/internal/providers/pluginfw/products/sharing/resource_share.go:449 +0x48e
github.com/databricks/terraform-provider-databricks/internal/providers/pluginfw/products/sharing.(*ShareResource).Read(0xc000527240, {0x1c50398?, 0xc000a31890?}, {{{{0x1c5b670, 0xc000a4c150}, {0x16fd920, 0xc000a41e30}}, {0x1c61390, 0xc0009b1ef0}}, 0x0, ...}, ...)
/home/runner/work/terraform-provider-databricks/terraform-provider-databricks/internal/providers/pluginfw/products/sharing/resource_share.go:281 +0x765
```
This leads to the default share resource having unstable implementation.
Panic can lead to bad state in TF since apply is stopped in between.
This change would be followed up by a patch release.
- No changes for users on version 1.85.0 and below which would upgrade
to patch release including this fix. Limit the impacted users by moving
back to SDKv2.
Impacted users with the issue of panic seems to have been able to
mitigate the issue by using older version of TF which uses SDKv2.
However, I am getting diff to create the share again. It seems like
SDKv2 is not able to use the state create by plugin framework. This
needs further investigation. To limit the impact of issue, we are
rolling back to the previous stable version.
## Tests
<!--
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->
Tests same as when SDKv2 was default.
Copy file name to clipboardExpand all lines: NEXT_CHANGELOG.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
# NEXT CHANGELOG
2
2
3
-
## Release v1.88.0
3
+
## Release v1.87.1
4
4
5
5
### Breaking Changes
6
+
Terraform databricks provider version 1.86.0 introduced changes to databricks_share resource leading to panic for some users while applying terraform. We are rolling back to SDKv2 implementation in this version. No change is expected for users who are upgrading to latest version from before 1.86.0. Users on 1.86.0 and not facing issues are suggested to not upgrade their version to this patch release. We are investigating the issue and will release a fix soon.
6
7
7
8
### New Features and Improvements
8
9
@@ -13,3 +14,4 @@
13
14
### Exporter
14
15
15
16
### Internal Changes
17
+
* Use SDKv2 Implementation for databricks_share resource as default ([#4931](https://github.com/databricks/terraform-provider-databricks/pull/4931))
0 commit comments