-
Notifications
You must be signed in to change notification settings - Fork 397
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
[Release] v1.49.0 #3752
[Release] v1.49.0 #3752
Conversation
### Internal Changes * Add Release tag ([#3748](#3748)). * Improve Changelog by grouping changes ([#3747](#3747)). * Upgrade Go SDK to v0.43.2 ([#3750](#3750)). ### Other Changes * Add `databricks_schema` data source ([#3732](#3732)). * Add new APIErrorBody struct and update deps ([#3745](#3745)). * Added support for binding storage credentials and external locations to specific workspaces ([#3678](#3678)). * Adds `databricks_volume` as data source ([#3211](#3211)). * Change TF registry ownership ([#3736](#3736)). * Exporter: Emit directories during the listing only if they are explicitly configured in `-listing` ([#3673](#3673)). * Exporter: export libraries specified as `requirements.txt` ([#3649](#3649)). * Exporter: fix generation of `run_as` blocks in `databricks_job` ([#3724](#3724)). * Exporter: use Go SDK structs for `databricks_job` resource ([#3727](#3727)). * Fix invalid priviledges in grants.md ([#3716](#3716)). * Make the schedule.pause_status field read-only ([#3692](#3692)). * Refactored `databricks_cluster(s)` data sources to Go SDK ([#3685](#3685)). * Renamed `databricks_catalog_workspace_binding` to `databricks_workspace_binding` ([#3703](#3703)). * Run goreleaser action in snapshot mode from merge queue ([#3646](#3646)). * Update cluster.md: add data_security_mode parameters `NONE` and `NO_ISOLATION` ([#3740](#3740)). * Upgrade databricks-sdk-go ([#3743](#3743)). * remove references to basic auth ([#3720](#3720)).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to split changelog further
Hi @alexott, yeah, I was looking into test infra issues, just updated the changelog. |
…ricks into prepare/1.48.3
We need to update this changelog as we merged a number of changes: |
…ricks into prepare/1.48.3
update: Waiting for #3690 to be merged before doing the release. |
…ricks into prepare/1.48.3
…ricks into prepare/1.48.3
…ricks into prepare/1.48.3
The release has been rebased + updated changelog for recently merged commits. There are few test failures that are known issues. Also some more failures in gcp-prod but they doesn't seem related to recent changes (they passed yesterday). Going ahead with release since these are mostly test infra issues. |
1.49.0
New Features and Improvements
databricks_dashboard
resource (#3729).databricks_schema
data source (#3732).databricks_volume
as data source (#3211).schedule.pause_status
field read-only (#3692).databricks_catalog_workspace_binding
todatabricks_workspace_binding
(#3703).cluster_name_contains
optional indatabricks_clusters
data source (#3760).databricks_dashboard
resource (#3762).Exporter
-listing
(#3673).requirements.txt
(#3649).run_as
blocks indatabricks_job
(#3724).databricks_job
resource (#3727).-listing
and-services
options (#3755).Documentation
NONE
andNO_ISOLATION
(#3740).Internal Changes
databricks_cluster(s)
data sources to Go SDK (#3685).dashboard_name
random in integration tests fordatabricks_dashboard
resource (#3763).