Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize AWS lambda naming #29749

Merged
merged 1 commit into from
Feb 24, 2023
Merged

Standardize AWS lambda naming #29749

merged 1 commit into from
Feb 24, 2023

Conversation

eladkal
Copy link
Contributor

@eladkal eladkal commented Feb 24, 2023

closes: #29677

I didn't change file names lambda_funciton.py to lambda.py as I think the current naming is fine (at least it does not contradict AIP-21) and lambda is a reserved word in Python so I think it's best not to create confusion around it.

cc @vincbeck


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Copy link
Contributor

@vincbeck vincbeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Thanks for doing it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename AWS lambda related resources
3 participants