This resource allows you to manage Databricks Git folders (formerly known as Databricks Repos).
You can declare Terraform-managed Git folder by specifying url
attribute of Git repository. In addition to that you may need to specify git_provider
attribute if Git provider doesn't belong to cloud Git providers (Github, GitLab, ...). If path
attribute isn't provided, then Git folder will be created in the default location:
resource "databricks_repo" "nutter_in_home" {
url = "https://github.com/user/demo.git"
}
The following arguments are supported:
url
- (Required) The URL of the Git Repository to clone from. If the value changes, Git folder is re-created.git_provider
- (Optional, if it's possible to detect Git provider by host name) case insensitive name of the Git provider. Following values are supported right now (could be a subject for a change, consult Repos API documentation): gitHub
, gitHubEnterprise
, bitbucketCloud
, bitbucketServer
, azureDevOpsServices
, gitLab
, gitLabEnterpriseEdition
, awsCodeCommit
.path
- (Optional) path to put the checked out Git folder. If not specified, , then the Git folder will be created in the default location. If the value changes, Git folder is re-created.branch
- (Optional) name of the branch for initial checkout. If not specified, the default branch of the repository will be used. Conflicts with tag
. If branch
is removed, and tag
isn't specified, then the repository will stay at the previously checked out state.tag
- (Optional) name of the tag for initial checkout. Conflicts with branch
.Optional sparse_checkout
configuration block contains attributes related to sparse checkout feature in Databricks Git folders. It supports following attributes:
patterns
- array of paths (directories) that will be used for sparse checkout. List of patterns could be updated in-place.Addition or removal of the sparse_checkout
configuration block will lead to recreation of the Git folder.
In addition to all arguments above, the following attributes are exported:
id
- Git folder identifiercommit_hash
- Hash of the HEAD commit at time of the last executed operation. It won't change if you manually perform pull operation via UI or APIworkspace_path
- path on Workspace File System (WSFS) in form of /Workspace
+ path
The resource can be imported using the Git folder ID (obtained via UI or using API)
$ terraform import databricks_repo.this repo_id
The following resources are often used in the same context: