✨ Source Zendesk Support: migration to low-code

[maxi297]

What

This is a stacked PR including all the part for https://github.com/airbytehq/airbyte-internal-issues/issues/11894:

• ✨ Source Zendesk Support: add tests and clean-up #55676
• ✨ Source Zendesk Support: migrate posts to low-code #55680
• ✨ Source Zendesk Support: migration posts child streams to low-code #55686
• ✨ Source Zendesk Support: user identities to low-code #55710
• ✨ Source Zendesk Support: tickets to low-code #55711
• ✨ Source Zendesk Support: article streams to low-code #55719
• ✨ Source Zendesk Support: ticket metrics streams to low-code #55795

How

See the stacked PRs for more information

Review guide

The changes have been reviewed in the stacked PRs

User Impact

This should speed up some of the streams as they would now run in the concurrent engine.

It also removes ignore_pagination.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

There are some streams where the state changes which means we can't revert.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 24, 2025 1:09pm

[maxi297]

Last round of regression tests (all considering state):

• posts: https://github.com/airbytehq/airbyte/actions/runs/14037185136
• post_comments: no data available for regression tests
• post_votes: no data available for regression tests
• post_comment_votes: no data available for regression tests
• user_identities: https://github.com/airbytehq/airbyte/actions/runs/14037198908
• tickets: https://github.com/airbytehq/airbyte/actions/runs/14037207144
• articles: https://github.com/airbytehq/airbyte/actions/runs/14037216587
• article_comments: no data available for regression tests
• article_votes: https://github.com/airbytehq/airbyte/actions/runs/14037230689
• article_comment_votes: no data available for regression tests
• ticket_metrics: https://github.com/airbytehq/airbyte/actions/runs/14037242383

EDIT: analysis
posts:

• There is client side filtering that exclude the cursor value (see this). The new version of the connector includes them which is fine as if there could be more records with the same datetime on updated_at
• The format changes from the record value like "2025-01-10T18:13:29Z" to %s as it is what we send to the API. I have confirmed that the target version supports both format.
• The state cursor value changes from the most_recent_cursor_value to the upper boundary of the requested slice

user_identities:

• Green in regression tests
• The format changes from the record value like "2025-01-10T18:13:29Z" to %s as it is what we send to the API. I have confirmed that the target version supports both format.

tickets:

• One more record in the target version which we assume was added during the sync or is the state value that was filtered on the client side for the control version
• The format changes from the record value like "2025-01-10T18:13:29Z" to %s as it is what we send to the API. I have confirmed that the target version supports both format.

articles:

• One more record in the target version which we assume was added during the sync or is the state value that was filtered on the client side for the control version
• The format changes from the record value like "2025-01-10T18:13:29Z" to %s as it is what we send to the API. I have confirmed that the target version supports both format.

article_votes:

• No testing candidates

ticket_metrics:

• One more record in the target version which we assume was added during the sync or is the state value that was filtered on the client side for the control version
• The state on the first sync goes from a int to a string (for example, {"_ab_updated_at": 1742826806} before and {"_ab_updated_at": "1742826806"} after)
• The state on subsequent syncs goes as per-partition state

Based on this, it seems like we are ready for a release tomorrow where most streams will be considered as a breaking change given the state changes.

[maxi297]

/approve-regression-tests

Check job output.

✅ Approving regression tests

[aldogonzalez8]

APPROVED