Remove overlooked pod_generator_deprecated.py
#46587
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ve_tests excluded
insomnes
requested review from
jedcunningham and
hussein-awala
as code owners
boring-cyborg
bot
added
the
provider:cncf-kubernetes
potiuk
approved these changes
Feb 8, 2025
hussein-awala
approved these changes
Feb 8, 2025
insomnes
changed the title
pod_generator_deprecate.py pod_generator_deprecated.py
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 17, 2025
* Delete `pod_generator_deprecated.py` missed during last deprecated modules deletion * Remove deleted deprecated files from test_providers_modules_should_have_tests excluded
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pod_generator_deprecated.pyfile was missed in the #43689providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/pod_generator_deprecated.py(Re-creation of messed up PR by new providers structure rebasing: #46377)
^ 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.rstor{issue_number}.significant.rst, in newsfragments.