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
[Fix] Throw an error when creating databricks_query and databricks_alert with already existing names (#4697)
## Changes
<!-- Summary of your changes that are easy to understand -->
Right now, when an object with the same name already exists in a
workspace, the Query and Alert APIs just create an object with a
different name (by appending `(1)` or something like that). This leads
to permanent configuration drift as TF will try to rename the object to
the name specified in the HCL.
P.S. Waiting for support this flag in the Update API as well...
## Tests
<!--
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->
- [x] `make test` run locally
- [ ] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] using Go SDK
- [ ] using TF Plugin Framework
---------
Co-authored-by: vuong-nguyen <[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
@@ -8,6 +8,8 @@
8
8
9
9
### Bug Fixes
10
10
11
+
* Fail when creating `databricks_query` and `databricks_alert` with already existing names [#4697](https://github.com/databricks/terraform-provider-databricks/pull/4697).
0 commit comments