Update minimum supported Terraform version in README.md
#4683
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
tanmay-db
approved these changes
May 1, 2025
alexott
approved these changes
May 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Currently, the minimum supported version of
terraformwith the Databricks TF Provider is documented as v1.0. However, there is an issue with too-strict validation of resources using SDKv2. This updates the guidance for customers to useterraformfrom v1.1.5, which mitigates this issue. Generally, new resources will be implemented using the Plugin Framework, which does have strict enforcement of these bugs. Over time, we will migrate resources to use the plugin framework, and when we do so, we will need to address them, but for now, the status quo is that they are tolerated. By using v1.1.5 and later, this will not result in errors in plan/apply steps.Tests
No tests needed, this is a docs-only change.