vincbeck opened a new issue, #29677:
URL: https://github.com/apache/airflow/issues/29677

   ### 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](airflow/providers/amazon/aws/operators/aws_lambda.py)
   
   ### 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?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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