fix: Set default dbt_version to latest and add diff logic to treat versionless and latest as equivalents #324
Conversation
This file contains 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
csquire
changed the title
chasewalden
approved these changes
Dec 12, 2024
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.
Updates the environment resource's dbt_version field to suppress the diff between
versionlessandlatest, so they are treat as equivalents when a comparison is performed. It also updates the default value for the environment resource's dbt_version tolatest, which should be backward compatible.This change was made because the provider's acceptance tests are using
versionless, and recently the dbt Cloud API began returninglatest, which caused the tests to fail.Resolves #320