fat-catTW commented on issue #71246:
URL: https://github.com/apache/airflow/issues/71246#issuecomment-5225206370

   Verified the following Amazon provider changes with 
`apache-airflow-providers-amazon==9.34.0rc2` on Airflow 3.3.0 in clean venvs. I 
also compared each relevant behavior with 
`apache-airflow-providers-amazon==9.33.0`.
   
   #70445: `AwsToAwsBaseOperator` destination connection fallback
   Checked `dest_aws_conn_id` fallback behavior when `dest_aws_conn_id` is 
omitted:
   - previous release `9.33.0`: after `source_aws_conn_id` changes from 
`'source_before_render'` to `'source_after_render'`, `dest_aws_conn_id` still 
returns `'source_before_render'`
   - RC `9.34.0rc2`: `dest_aws_conn_id` follows the updated source and returns 
`'source_after_render'`
   
   Also checked that explicit `dest_aws_conn_id=None` and templated 
`dest_aws_conn_id` are preserved during operator construction.
   
   #70440: templated validation fields in AppFlow operators
   Checked `AppflowRunDailyOperator` with templated `source`, `source_field`, 
and `filter_date`.
   
   Previous release `9.33.0` rejects the operator during construction:
   `Source {{ params.source }} is not supported for AppflowRunDailyOperator!`
   
   RC `9.34.0rc2` allows construction, renders the fields, validates after 
rendering, and executes the patched run path with:
   - `source='salesforce'`
   - `source_field='CreatedDate'`
   - `filter_date='2022-05-26T00:00:00+00:00`
   
   #70464: deferred ECS logs region selection
   Checked `EcsRunTaskOperator.execute_complete()` when 
`region_name='task-region'` and `awslogs_region='logs-region'`.
   
   Previous release `9.33.0` calls `AwsLogsHook` with 
`region_name='task-region'`.
   
   RC `9.34.0rc2` calls `AwsLogsHook` with `region_name='logs-region'` and 
returns the expected log output.
   
   Result: all three work as expected.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to