Add FivetranOperatorAsync hook and trigger to handle reschedule changes

[sunank200]

• Add FivetranOperatorAsync to handle reschedule mode
• When connector has schedule_type manual and sync_status reschedule, connector will hang as Fivetran expects manual restart. This pr automatically (or optionally manually) handles that restart.
• Add tests
  closes: FivetranOperatorAsync waits forever in case of reschedule #21

[pankajastro]

shall we add this param here too while initialising trigger

airflow-provider-fivetran-async/fivetran_provider_async/sensors.py

Line 35 in 8cdf25d

trigger=FivetranTrigger(

airflow-provider-fivetran-async/fivetran_provider_async/operators.py

Line 35 in 8cdf25d

trigger=FivetranTrigger(

[sunank200]

shall we add this param here too while initialising trigger

airflow-provider-fivetran-async/fivetran_provider_async/sensors.py

Line 35 in 8cdf25d

trigger=FivetranTrigger(

airflow-provider-fivetran-async/fivetran_provider_async/operators.py

Line 35 in 8cdf25d

trigger=FivetranTrigger(

Added the change

[phanikumv]

Dont we need tests to be added for operator and sensor for reschedule change?

[sunank200]

Dont we need tests to be added for operator and sensor for reschedule change?

I have added the relevant tests in hook and triggerer. I can add tests in for sensor and operator as well

[pankajkoti]

I have the below questions:

1. Does rescheduled_for exists & applies for connector_details["schedule_type"] == "manual" in FiveTran?
2. Were we able to test the issue fix E2E with a DAG mentioned in the PR description wrt
   When connector has schedule_type manual and sync_status reschedule, connector will hang as Fivetran expects manual restart. This pr automatically (or optionally manually) handles that restart.?

If the answer is yes to both the questions, then the changes look good to me.

[sunank200]

I have the below questions:

1. Does rescheduled_for exists & applies for connector_details["schedule_type"] == "manual" in FiveTran?
   @pankajkoti

1. Yes rescheduled_for and `connector_details["schedule_type"] == "manual" exists in Fivetran as per the API documentation as well: https://fivetran.com/docs/rest-api/connectors#fields

[sunank200]

I have the below questions:

2. Were we able to test the issue fix E2E with a DAG mentioned in the PR description wrt
   When connector has schedule_type manual and sync_status reschedule, connector will hang as Fivetran expects manual restart. This pr automatically (or optionally manually) handles that restart.?

If the answer is yes to both the questions, then the changes look good to me.

I have tested it locally using the following task:

fivetran_async_op = FivetranOperatorAsync(
        task_id="fivetran_async_op",
        connector_id="rolled_praising",
        fivetran_conn_id="fivetran_default",
        reschedule_wait_time=60,
        schedule_type="manual"
    )

In this PR, we automatically handle the case of restart of the sync.

[sunank200]

Update the tests

@phanikumv I have updated the test for various scenarios: 4539e03