Multiple AWS connections support in DynamoDBToS3Operator

[dym-ok]

We're using DynamoDBToS3Operator to copy data from a DynamoDB table in one AWS account, where we assume an IAM role, to an S3 bucket in another account.

For that we have to use a slightly modified version of this operator that uses two different AWS connections, with a second one provided as aws_dynamodb_conn_id constructor argument.

I think it might be a typical use case and would be willing to provide a PR for such extension. Does anybody find this use case common enough for such a change?

[Taragolis]

I think it might be a typical use case and would be willing to provide a PR for such extension. Does anybody find this use case common enough for such a change?

Feel free to make a PR, that is how Airflow evolve in general:

• User has use-case/issue
• Make a PR
• Discussion in the PR (if required)
• PR merged in main
• Changes added in new version of specific provider or core

If it would your first PR to Airflow, I suggest to read Contributor's Quick Start and all other relevant docs, e.g. Testing, Static code checks

[dym-ok]

Thanks, @Taragolis I'll get onto it.

[Taragolis]

One thing it would be nice if changes keep compatibility with current implementation.

In additional might be a good idea to join to the Apache Airflow Community Slack, for development questions useful channels are: development and airflow-breeze

[dym-ok]

Thanks a lot for your tips, @Taragolis!