Airflow api-server missing `--log-config` argument

[jnstockley]

Apache Airflow version

3.0.3

If "Other Airflow 2 version" selected, which one?

No response

What happened?

According to the docs here, https://airflow.apache.org/docs/apache-airflow/stable/cli-and-env-variables-ref.html#api-server, the api-server sub-command should have a name argument of --log-config but when the command field in the docker compose file is set to api-server --log-config=<file_path> the following error is shown airflow command error: unrecognized arguments: --log-config=<file_path>, see help above. I have also tried doing api-server --log-config <file_path> with a similar error message airflow command error: unrecognized arguments: --log-config <file_path>, see help above.

What you think should happen instead?

Preferably the api-server component should be updated to re-include this named argument, with the help message updated, or the docs should be updated to remove this name argument.

How to reproduce

In the provided docker-compose.yaml file, update the airflow-apiserver serivce command to be api-server --log-config <file_path>

Operating System

Debian

Versions of Apache Airflow Providers

No response

Deployment

Other Docker-based deployment

Deployment details

Custom docker image based on official docker image

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[potiuk]

We won't do much with it. This is because the recent doc refresh (for other reasons) accidentally picked this one #53372 -> which is coming in 3.0.4. Maybe we should remove it manually from generated docs, but that's a little nuance and It looks like 3.0.4 is coming shortly so might not be worth it.

[jnstockley]

@potiuk Thanks, just making sure I understand, that CLI argument is not something that is planned on being re-added/fixed? If that is the case, how can we change the log format for uvicorn?

[potiuk]

Quite the contrary. It is coming in 3.0.4 . See the linked PR

[potiuk]

And with #53668 we might have a nice mechanism to fix it in released docs. I will try it after we test it when fixing hive documentation issue we had.