alanatlemba opened a new pull request, #26982: URL: https://github.com/apache/airflow/pull/26982
<!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> closes: #23529 This is my first PR for a mainstream large scale open source project, let alone Airflow. Sorry in advance if I've done anything improper, and thanks for your patience. Thank you @nitinmuteja & @lior1990 for doing much of the work. This is following up on a this closed/abandoned PR: https://github.com/apache/airflow/pull/23531 Here is how I tested: `breeze testing tests --test-type "Providers[cncf]"` `breeze k8s run-complete-tests` I'm not sure if further testing is necessary. Should I bother making sure that I see a mapped k8s pod operator dag run with the expected resources? I may need some help working through that. :) --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). 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](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
