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
[Exporter] **Breaking change**: Move databricks_workspace_file to a separate service (#4118)
## Changes
<!-- Summary of your changes that are easy to understand -->
Move `databricks_workspace_file` to a separate service `wsfiles`, so we
can list and export them separately from notebooks. If you used
`notebooks` in `-listing` or `-services` options, then you need to
append `wsfiles` to these options.
## Tests
<!--
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->
- [x] `make test` run locally
- [x] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] relevant acceptance tests are passing
- [ ] using Go SDK
@@ -148,6 +148,7 @@ Services are just logical groups of resources used for filtering and organizatio
148
148
*`users` - [databricks_user](../resources/user.md) and [databricks_service_principal](../resources/service_principal.md) are written to their own file, simply because of their amount. If you use SCIM provisioning, migrating workspaces is the only use case for importing `users` service.
149
149
*`vector-search` - **listing** exports [databricks_vector_search_endpoint](../resources/vector_search_endpoint.md) and [databricks_vector_search_index](../resources/vector_search_index.md)
150
150
*`workspace` - **listing**[databricks_workspace_conf](../resources/workspace_conf.md) and [databricks_global_init_script](../resources/global_init_script.md)
0 commit comments