Databricks SDK Go v0.138.0 addresses config profile loading
Databricks SDK Go v0.138.0 fixes an issue where the configuration file loader would not set the profile name when using the legacy fallback. This change ensures consumers can correctly derive a per-profile identifier, preventing issues where writes under the 'DEFAULT' profile could not be found by subsequent reads. This fix is relevant for users of the Databricks CLI and any applications deriving profile identifiers from the SDK's configuration.
Fixes (1) ›
config: The config-file loader now sets cfg.Profile to "DEFAULT" on the legacy fallback (no profile requested, no [__settings__].default_profile set, [DEFAULT] section loaded). Previously the loader silently used [DEFAULT]'s values but left cfg.Profile empty. Consumers that derive a per-profile identifier from cfg.Profile (e.g. the Databricks CLI's U2M OAuth cache key) need the resolved name to match across the login and read flows; without this fix a write under "DEFAULT" could not be found by a no-flag read
https://github.com/databricks/databricks-sdk-go/releases/tag/v0.138.0
Related releases
- Building an AI-Forward Healthcare Organization on Data and Governance Databricks Blog ·
- Databricks Accelerates Agentic Media Buying with New Reference Implementation Databricks Blog ·
- NBCUniversal Migrates to Databricks Lakehouse for Scalable Analytics Databricks Blog ·
- Databricks SDK for Python v0.123.0: API changes and breaking updates Databricks Python SDK Releases ·
- Databricks Go SDK v0.167.0 Adds Cloud Provider Auth Fields Databricks Go SDK Releases ·
- Databricks SDK Java v0.138.0 Adds Model Provider Config Fields Databricks Java SDK Releases ·