mik-laj opened a new pull request #16258: URL: https://github.com/apache/airflow/pull/16258
I've slightly improved the argument handling to better handle edge cases. Now, the following command has the same exit code and output ``` docker run --rm my-airflow:2.1.0 docker run --rm my-airflow:2.1.0 airflow airflow ``` The previous one, each of these commands, behaved a bit differently. ``docker run --rm my-airflow:2.1.0``behaved identically to airflow --help i.e. zero exit code and no warning about missing argument ``docker run --rm my-airflow:2.1.0 airflow`` display error - ``/entrypoint: line 326: 2: unbound variable`` and returns non-zero exit code. Close: https://github.com/apache/airflow/issues/16252 ``docker run --rm my-airflow:2.1.0 bash -c "airflow"`` had behavior identical to the `airflow` command <!-- 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/main/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/main/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]
