Skip to content

Upgrade Terraform dependency to v1.12.2 - #3040

Closed
pietern wants to merge 4 commits into
mainfrom
bump-tf-latest
Closed

Upgrade Terraform dependency to v1.12.2#3040
pietern wants to merge 4 commits into
mainfrom
bump-tf-latest

Conversation

@pietern

Copy link
Copy Markdown
Contributor

Changes

This change updates the Terraform dependency to 1.12.2 (latest).

@pietern
pieterntemporarily deployed to test-trigger-is June 12, 2025 00:31 — with GitHub Actions Inactive
@pietern
pieterntemporarily deployed to test-trigger-is June 12, 2025 01:00 — with GitHub Actions Inactive

@denikdenik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Surprised nothing breaks :)

@denik

Copy link
Copy Markdown
Contributor

NEXT_CHANGELOG.md?

@pieternpietern changed the title Update Terraform dependency to 1.12.2Upgrade Terraform dependency to v1.12.2Jun 16, 2025
@pietern
pieterntemporarily deployed to test-trigger-is June 16, 2025 10:14 — with GitHub Actions Inactive
pietern added a commit that referenced this pull request Jun 18, 2025
## Changes
Previously, the CLI would use the Terraform binary at
`DATABRICKS_TF_EXEC_PATH` only if the `DATABRICKS_TF_VERSION`
environment variable was set and matched the _built-in default version_.
It was built such that we could ship all binaries with the VS Code
extension to avoid re-downloading (see #1294).
This change expands the scope of these variables and makes them
composable. Now, you can:
1. Configure `DATABRICKS_TF_VERSION` to override the Terraform version
to use
2. Configure `DATABRICKS_TF_EXEC_PATH` to configure the path to an
existing Terraform binary
If 1 is used alone, the CLI will download the specified version. If 2 is
used alone, the CLI will execute the specified binary to confirm that it
matches the _built-in default version_. If both are used, the CLI will
execute the specified binary to confirm that it matches the specified
version.
## Why
To allow users to use newer version of the Terraform CLI.
## Tests
* Unit tests pass
* Integration tests with the latest Terraform version (#3040)
@pietern

Copy link
Copy Markdown
ContributorAuthor

Superseded by #3069. This gives users more control, while sticking to the existing default.

@pieternpietern closed this Jun 18, 2025
@pietern
pietern deleted the bump-tf-latest branch June 18, 2025 14:08
denik pushed a commit that referenced this pull request May 20, 2026
## Changes
Previously, the CLI would use the Terraform binary at
`DATABRICKS_TF_EXEC_PATH` only if the `DATABRICKS_TF_VERSION`
environment variable was set and matched the _built-in default version_.
It was built such that we could ship all binaries with the VS Code
extension to avoid re-downloading (see #1294).
This change expands the scope of these variables and makes them
composable. Now, you can:
1. Configure `DATABRICKS_TF_VERSION` to override the Terraform version
to use
2. Configure `DATABRICKS_TF_EXEC_PATH` to configure the path to an
existing Terraform binary
If 1 is used alone, the CLI will download the specified version. If 2 is
used alone, the CLI will execute the specified binary to confirm that it
matches the _built-in default version_. If both are used, the CLI will
execute the specified binary to confirm that it matches the specified
version.
## Why
To allow users to use newer version of the Terraform CLI.
## Tests
* Unit tests pass
* Integration tests with the latest Terraform version (#3040)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@pietern@denik@shreyas-goenka