migrate to dbt v3 api for project endpoints #39214
Merged
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
|
The list below shows what has been migrated to v3 API.
|
phanikumv
approved these changes
Apr 25, 2024
jedcunningham
approved these changes
Apr 27, 2024
… and {account_id}/projects/{project_id}/
jedcunningham
approved these changes
Apr 29, 2024
Lee-W
changed the title
RodrigoGanancia
pushed a commit
to RodrigoGanancia/airflow
that referenced
this pull request
May 10, 2024
* feat(providers/dbt): migrate to v3 api for /, {account_id}/projects/, and {account_id}/projects/{project_id}/
* refactor(dbt): make all arguments in _run_and_get_response keyword only argument
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.
As suggested in https://github.com/dbt-labs/dbt-cloud-openapi-spec/blob/02726f68474d69844bdf87ce267d5ba9218c171c/openapi-v2.yaml#L44, some of the dbt v2 API has been deprecated and v3 is suggested
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.