roykoand opened a new issue, #59794: URL: https://github.com/apache/airflow/issues/59794
### What do you see as an issue? The CLI help text for date arguments (e.g., `--start-date`/`--end-date`) only documents the `YYYY-MM-DD` format: https://github.com/apache/airflow/blob/ac085a425652d16b5fff17f8e937938c7d47b868/airflow-core/src/airflow/cli/cli_config.py#L170-L171 However, the actual implementation uses `pendelum.parse` which accepts a much wider variety of formats beyond what's documented: https://github.com/apache/airflow/blob/ac085a425652d16b5fff17f8e937938c7d47b868/shared/timezones/src/airflow_shared/timezones/timezone.py#L191 With `strict=False` it accepts a ton of different formats such as: ``` RFC 3339 2025-12-24T08:30:00Z 2025-12-24T08:30:00-05:00 ISO 8601 2025-12-24 20251224 2025-W52 08:30:00 ``` ### Solving the problem I suggest the following help text for discussion: ``` -s, --start-date Override start_date. Common formats: YYYY-MM-DD YYYY-MM-DDTHH:MM:SS YYYY-MM-DDTHH:MM:SS±HH:MM Supports any format accepted by pendulum.parse() ``` Additionally, I think accepting all formats supported by `pendulum.parse()` may not be ideal, as it could lead to ambiguity and confusion. We should consider limiting the accepted formats to a defined subset to ensure consistency and clarity. ### Anything else _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
