ES-1862841

We are actively investigating an issue with the Databricks service.

Next Update

We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary
Starting at 18 April 2026 21:50 UTC, customers using the Declarative Automation Bundles (formerly known as Databricks Asset Bundles) for automated CI/CD bundle deployments may experience delays or failures impacting deployments that require downloading and verifying the Terraform binary. This issue is caused by the GPG key used for checksum verification, provided by Hashicorp, having expired on April 18.

Symptoms
Customers may observe:

Failures in CI/CD pipelines when executing Databricks CLI bundle deployment commands.
Errors indicating a failure in GPG checksum verification during the installation process for the Terraform binary.
A widespread inability to perform automated deployments.


Recommendations

Workaround: For an immediate temporary solution, customers can manually download and install the Terraform binary themselves, perform their own security verification, and then point their bundle configuration to the locally installed Terraform version.
Future Upgrade: Once a fixed version of the CLI is released, customers who are not pinning their CLI version should upgrade to resolve the issue.


Current Status
Our team is actively investigating and working on a resolution. Engineering is focused on developing and releasing a fix.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary
Starting at 18 April 2026 21:50 UTC, customers using the Declarative Automation Bundles (formerly known as Databricks Asset Bundles) for automated CI/CD bundle deployments may experience delays or failures impacting deployments that require downloading and verifying the Terraform binary. This issue is caused by the GPG key used for checksum verification, provided by Hashicorp, having expired on April 18.

Symptoms
Customers may observe:

Failures in CI/CD pipelines when executing Databricks CLI bundle deployment commands.
Errors indicating a failure in GPG checksum verification during the installation process for the Terraform binary.
A widespread inability to perform automated deployments.


Recommendations

Workaround: For an immediate temporary solution, customers can manually download and install the Terraform binary themselves, perform their own security verification, and then point their bundle configuration to the locally installed Terraform version.
Future Upgrade: Once a fixed version of the CLI is released, customers who are not pinning their CLI version should upgrade to resolve the issue.


Current Status
Our engineering team has identified a fix that involves incorporating the new public key into the Databricks CLI code, which bypasses the expired GPG key check. The fix has already been released on the latest CLI version i.e., 0.297.2
We are actively working on releasing patch versions for the affected CLI.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status. Keep placeholder for info you don't have.

Starting at 18 April 2026 21:50 UTC, customers using the Declarative Automation Bundles (formerly known as Databricks Asset Bundles) for automated CI/CD bundle deployments may experience delays or failures impacting deployments that require downloading and verifying the Terraform binary. This issue is caused by the GPG key used for checksum verification, provided by Hashicorp, having expired on April 18.

Symptoms
Customers may observe:
Failures in CI/CD pipelines when executing Databricks CLI bundle deployment commands.
Errors indicating a failure in GPG checksum verification during the installation process for the Terraform binary.
A widespread inability to perform automated deployments.


Recommendations
Workaround: For an immediate temporary solution, customers can manually download and install the Terraform binary themselves, perform their own security verification, and then point their bundle configuration to the locally installed Terraform version.
Upgrade: Customers using the latest CLI version should upgrade to the latest version 0.297.2 to resolve the issue. Customers on older versions should monitor for patch releases and upgrade when available.


Current Status
The fix has been released for the latest Databricks CLI version, 0.297.2, resolving the issue for customers using or upgrading to the latest version. For customers who pin to older versions, our engineering team is actively working on applying and releasing the patch to those minor versions.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at 18 April 2026 21:50 UTC, customers using the Declarative Automation Bundles (formerly known as Databricks Asset Bundles) for automated CI/CD bundle deployments may experience delays or failures impacting deployments that require downloading and verifying the Terraform binary. This issue is caused by the GPG key used for checksum verification, provided by Hashicorp, having expired on April 18.

Symptoms
Customers may observe:
Failures in CI/CD pipelines when executing Databricks CLI bundle deployment commands.
Errors indicating a failure in GPG checksum verification during the installation process for the Terraform binary.
A widespread inability to perform automated deployments.

Recommendations
Workaround: For an immediate temporary solution, customers can manually download and install the Terraform binary themselves, perform their own security verification, and then point their bundle configuration to the locally installed Terraform version.
Upgrade: Customers using the latest CLI version should upgrade to the latest version 0.297.2 to resolve the issue. Customers on older versions should monitor for patch releases and upgrade when available.

Current Status
The fix has been released for the latest Databricks CLI version, 0.297.2, resolving the issue for customers using or upgrading to the latest version. For customers who pin to older versions, our engineering team is actively working on applying and releasing the patch to those minor versions.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.