HsiuChuanHsu opened a new pull request, #53459:
URL: https://github.com/apache/airflow/pull/53459
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
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:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
## Description
This pull request addresses issue
[#47702](https://github.com/apache/airflow/issues/47702) by adding validation
for the `executor_config` dictionary in the `BaseOperator` class of
`task-sdk/src/airflow/sdk/bases/operator.py`. The change ensures that only the
allowed keys (`pod_override` and `pod_template_file`) are used in
`executor_config`. If invalid keys are present, an `AirflowException` is raised
with a descriptive error message, preventing silent failures and providing
clear feedback to users.
## Changes:
- Added a new method validate_executor_config in
task-sdk/src/airflow/sdk/bases/operator.py to validate the executor_config
dictionary.
- The validation checks that executor_config is a dictionary and only
contains the keys pod_override or pod_template_file.
- If invalid keys are found, an AirflowException is raised with an error
message that includes the task ID, DAG ID (if available), and the list of
invalid keys.
## Additional Notes:
The error would be displayed in the `import-errors` section of the Airflow
UI.
<img width="888" height="468" alt="Screenshot 2025-07-16 at 7 21 40 AM"
src="https://github.com/user-attachments/assets/b7f97f49-7e9d-46ef-aa6b-4cb11cf1bff6";
/>
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.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
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/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]
