databricks/terraform-provider-databricks

Databricks Terraform Provider

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Added to GitGenius on January 4th, 2025
Created on February 13th, 2020
Open Issues & Pull Requests: 668 (+0)
Number of forks: 547
Total Stargazers: 596 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.4 days
Mean response time: 155.9 days
90th percentile: 656.7 days
Tracked items: 838

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "platform bug" is answered fastest, typically in about 10 hours, while "Bug" waits about 20 months. 71% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 500
New in 7 days: 1
Closed in 7 days: 2
Avg open age: 481 days
Stale 30+ days: 486
Stale 90+ days: 439

Recent activity

Opened in 7 days: 1
Closed in 7 days: 2
Comments in 7 days: 4
Events in 7 days: 14

Top labels

  • feature (412)
  • docs (159)
  • Bug (110)
  • exporter (82)
  • azure (80)
  • invalid (78)
  • needs-api (70)
  • autogen (50)

Detailed Description

The Databricks Terraform Provider is a Terraform plugin written in Go that enables infrastructure-as-code management of Databricks workspaces across AWS, Azure, and GCP cloud platforms. The provider allows users to define and provision Databricks resources using Terraform configuration files, supporting Terraform version 1.1.5 and newer. It is distributed through the official Terraform Registry and includes comprehensive documentation covering platform-specific tutorials for AWS and Azure, end-to-end workspace management guidance, authentication setup, and troubleshooting resources.

The provider supports multiple authentication methods and requires users to supply personal access tokens for API communication with Databricks workspaces. The repository includes sample Terraform configurations and migration guidance for users transitioning from the earlier databrickslabs namespace to the current databricks namespace under the official Databricks organization. The provider also offers experimental OpenTofu compatibility, though this integration is not actively tested and remains in an experimental state.

A notable feature is the experimental Terraform exporter functionality, which allows users to export existing Databricks resources into Terraform configuration code. The provider handles specialized field types including Go-style duration strings for time-based configurations, RFC3339 formatted timestamps with timezone information, and JSON-encoded value fields with automatic normalization and validation.

GitGenius activity data reveals this is an actively maintained project with substantial community engagement.

This suggests the provider attracts contributors with diverse technical backgrounds and experience across multiple major open-source projects.

The provider is classified across multiple infrastructure and cloud automation domains including cloud orchestration, infrastructure-as-code, multi-cloud resource management, and configuration management. It specifically addresses AWS, Azure, and GCP integration scenarios, making it relevant for organizations deploying Databricks across heterogeneous cloud environments. The repository includes comprehensive contributing and development guidelines for users interested in building from source or extending the provider's functionality.