potiuk opened a new pull request #14508: URL: https://github.com/apache/airflow/pull/14508
Also clarified a little unclear change resulting from #14480 which did not carry an explanation why we want to return exit code 64. Explanation is added back and explicit check for False is used. It is not clear how result callback function behaves when comand returns no value (it could easily be called with result = None). This is not clear in the click documentation, so expicit check for False value better reflects the intention here. Breeze commands and documentation is also updated so that both invocation via breeze (which assures coommon import check) and manual execution for debugging can take advantage of it. <!-- 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 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/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+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 [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.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. For queries about this service, please contact Infrastructure at: [email protected]
