Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix wrong payload set when reuse_existing_run set to True in DbtCloudRunJobOperator #39271

Conversation

Lee-W
Copy link
Member

@Lee-W Lee-W commented Apr 26, 2024

status__in should be used instead https://docs.getdbt.com/dbt-cloud/api-v2#/operations/List%20Runs


^ 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.rst or {issue_number}.significant.rst, in newsfragments.

@Lee-W Lee-W requested a review from josh-fell as a code owner April 26, 2024 04:42
@Lee-W Lee-W changed the title fix fix reuse_existing_run wrong payload sent DbtCloudRunJobOperator fix wrong payload setn when reuse_existing_run set to True in DbtCloudRunJobOperator Apr 26, 2024
@Lee-W Lee-W force-pushed the fix-reuse_existing_run-wrong-payload-in-DbtCloudRunJobOperator branch from 75e8c17 to d1fe16f Compare April 26, 2024 04:43
@Lee-W Lee-W changed the title fix wrong payload setn when reuse_existing_run set to True in DbtCloudRunJobOperator fix wrong payload set when reuse_existing_run set to True in DbtCloudRunJobOperator Apr 26, 2024
@eladkal eladkal merged commit 79b5443 into apache:main Apr 30, 2024
40 checks passed
@Lee-W Lee-W deleted the fix-reuse_existing_run-wrong-payload-in-DbtCloudRunJobOperator branch June 5, 2024 06:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants