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

Update Zendesk example DAG to use TaskFlow API #21411

Merged
merged 1 commit into from
Feb 10, 2022

Conversation

josh-fell
Copy link
Contributor

Related: #9415

Staying consistent with previous work that was done to convert example DAGs to the functional style of authoring, this PR updates the example DAG for Zendesk to use the TaskFlow API.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.

@josh-fell josh-fell force-pushed the zendesk-example-dag-taskflow-api branch from c49e5f4 to 5ba366c Compare February 10, 2022 19:33
@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label Feb 10, 2022
@github-actions
Copy link

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

@eladkal eladkal merged commit e052fb5 into apache:main Feb 10, 2022
@josh-fell josh-fell deleted the zendesk-example-dag-taskflow-api branch February 10, 2022 21:27
ferruzzi pushed a commit to ferruzzi/airflow that referenced this pull request Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers okay to merge It's ok to merge this PR as it does not require more tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants