ferruzzi commented on issue #22438:
URL: https://github.com/apache/airflow/issues/22438#issuecomment-1281561001
Quick update, the following are not checked off above:
- airflow/providers/amazon/aws/example_dags/example_emr.py
- @syedahsn is working on this one right now.
- airflow/providers/amazon/aws/example_dags/example_eks_templated.py
- All of the operators in this DAG are tested in other system tests which
have already been converted, so there is no added benefit to converting this
one. It was initially a demo of how to use Jinja templating that I wrote and
contributed when I was learning how to use it, so I do think it still has value
as an example DAG. Should we delete this file, move it somewhere else, or just
leave it? I feel like if we keep it, then "Example DAGs" is exactly where it
should live. It uses AWS operators, but it's specifically an AWS example (if
that makes sense?) so maybe move it to a more generic location?
All of the remaining files were deemed out of scope for the current
conversion project since they require external services/accounts/servers/etc
(for example: requires a MongoDB account, a GCP account, hosting an SFTP
server, etc) and we won't be able to commit to running/maintaining them on a
regular basis. We may add them at a later date, but they won't be part of this
big push.
- airflow/providers/amazon/aws/example_dags/example_s3_to_sftp.py
- airflow/providers/amazon/aws/example_dags/example_sftp_to_s3.py
- airflow/providers/amazon/aws/example_dags/example_imap_attachment_to_s3.py
- I think this one goes here because it needed an SMTP server configured
but I'm not certain?
- airflow/providers/amazon/aws/example_dags/example_glacier_to_gcs.py
- airflow/providers/amazon/aws/example_dags/example_salesforce_to_s3.py
--
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]
