🎉 Source Zendesk Chat: migrate to YamlDeclarativeSource (Low-code)

[bazarnov]

What

Resolving: https://github.com/airbytehq/airbyte-internal-issues/issues/6468

How

• by using the airbyte-cdk.declarative (Low-code)
• added missing pk for agents_timeline stream: id to the schema
• added 5 custom components to cover the migration:
  • bans_record_extractor - custom record_extractor for bans stream
  • id_incremental_cursor - custom cursor to provide the ability to pull data using id(int) as cursor.
  • id_offset_pagination_strategy - the pagination strategy that uses the id offset from the records and uses it as next_page_token
  • time_offset_pagination_strategy - the pagination strategy that uses timestamp from response as the next_page_token
  • timestamp_based_cursor - provides the ability to track the cursor_field values from the record instead of stream_slices and making adjustments to the request_params needed for agent_timeline and chats streams
• covered all custom components with unit_tests
• removed leftovers from the previous code-base
• added migrations.md to pass QA checks as of breaking change
• updated expected records to match the changes

🚨 User Impact 🚨

The breaking changes are avoided, with additional RECORD Transformations.

[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 20, 2024 8:19pm

[maxi297]

Thanks @bazarnov ! Can you acknowledge that the change in behaviors that were identified are fine?

[maxi297]

Conditional approval given:

• Comment about id changing is resolved
• Comment about filtering/ordering is resolve
• Migration is properly documented

Thanks a lot @bazarnov !

[maxi297]

Discrepancies I still see:

• [fine with this] accounts, goals, roles, shortcuts, skills and triggers: limit has been removed
• [fine with this] agent_timeline and chats: start_time query param is not the same but we've identify it only affects execution outside of docker
• [fine with this] bans: caused by a bug in the previous implementation

Hence, I confirm that this change is all good. Thanks @bazarnov !