harrisjoseph opened a new issue, #25905:
URL: https://github.com/apache/airflow/issues/25905
### Description
`airflow dags trigger` creates dag_runs with a specified `execution_date`.
Since the deprecation of `execution_date`, some logic in the
`infer_manual_data_interval()` method has been used to translate between
`execution_date` and the new `logical_start_date` + `logical_end_date` fields.
This logic sometimes produces incorrect dates.
We should add a new CLI & API endpoint + code path that accepts explicit
`logical_start_date` + `logical_end_date` values, and provide a path that
doesn't rely on the deprecated `execution_date`.
I'd like to find some time to do this myself and raise a PR, but can't
guarantee that I'll get around to it in the next few months
### Use case/motivation
```
airflow dags trigger --logical_start_date {date} --logical_end_date {date
## produces a dag_run with those dates
```
Rather than the behaviour:
```
airflow dags trigger --executiond_date {date}
# Produces a dag_run with dates that are sometimes correct, sometimes
incorrect, depending on whether "infer_manual_data_interval" likes them or not
```
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] 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]
