Apache Airflow Provider(s)
amazon
Versions of Apache Airflow Providers
No response
Apache Airflow version
2.5.0
Operating System
MacOS
Deployment
Virtualenv installation
Deployment details
AWS Lambda in Amazon provider package do not follow the convention #20296. Hook, operators and sensors related to AWS lambda need to be renamed to follow this convention. Here are the proposed changes in order to fix it:
- Rename
airflow/providers/amazon/aws/operators/lambda_function.py to airflow/providers/amazon/aws/operators/lambda.py
- Rename
airflow/providers/amazon/aws/sensors/lambda_function.py to airflow/providers/amazon/aws/sensors/lambda.py
- Rename
airflow/providers/amazon/aws/hooks/lambda_function.py to airflow/providers/amazon/aws/hooks/lambda.py
- Rename
AwsLambdaInvokeFunctionOperator to LambdaInvokeFunctionOperator
Since all these changes are breaking changes, it will have to be done following the deprecation pattern:
- Copy/paste the files with the new name
- Update the existing hook, operators and sensors to inherit from these new classes
- Deprecate these classes by sending deprecation warnings. See an example here
What happened
No response
What you think should happen instead
No response
How to reproduce
N/A
Anything else
No response
Are you willing to submit PR?
Code of Conduct
Apache Airflow Provider(s)
amazon
Versions of Apache Airflow Providers
No response
Apache Airflow version
2.5.0
Operating System
MacOS
Deployment
Virtualenv installation
Deployment details
AWS Lambda in Amazon provider package do not follow the convention #20296. Hook, operators and sensors related to AWS lambda need to be renamed to follow this convention. Here are the proposed changes in order to fix it:
airflow/providers/amazon/aws/operators/lambda_function.pytoairflow/providers/amazon/aws/operators/lambda.pyairflow/providers/amazon/aws/sensors/lambda_function.pytoairflow/providers/amazon/aws/sensors/lambda.pyairflow/providers/amazon/aws/hooks/lambda_function.pytoairflow/providers/amazon/aws/hooks/lambda.pyAwsLambdaInvokeFunctionOperatortoLambdaInvokeFunctionOperatorSince all these changes are breaking changes, it will have to be done following the deprecation pattern:
What happened
No response
What you think should happen instead
No response
How to reproduce
N/A
Anything else
No response
Are you willing to submit PR?
Code of Conduct