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] Caching of group membership in databricks_group_member (#4581)
## Changes
On the installations with large number of users the provider creates a
large number of API calls to the Databricks API leading to slow
deployments. The provider also requests all members for each group
membership check.
In this change group member resource use expiring caches - in our case
we halved the default deployment times on existing installation and
eliminated Databricks API throttling.
I am also looking for some guidance on how to make this change more
generic.
## Tests
We run this provider in production with about 800 users and ~100 groups.
- [x] `make test` run locally
- [ ] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [x] using Go SDK
- [x] using TF Plugin Framework
---------
Co-authored-by: Ruslan Abdulkhalikov <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Alex Ott <[email protected]>
Co-authored-by: vuong-nguyen <[email protected]>
Co-authored-by: Alex Ott <[email protected]>
Co-authored-by: Miles Yucht <[email protected]>
Copy file name to clipboardExpand all lines: NEXT_CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,3 +13,5 @@
13
13
### Exporter
14
14
15
15
### Internal Changes
16
+
17
+
* Caching group membership in `databricks_group_member` to improve performance ([#4581](https://github.com/databricks/terraform-provider-databricks/pull/4581)).
0 commit comments