I'm aware that a DAG scheduled to start at time X with interval Y will first run at time X + Y. The documentation describes this:
"Note that if you run a DAG on a schedule_interval of one day, the run stamped 2016-01-01 will be trigger soon after 2016-01-01T23:59. In other words, the job instance is started once the period it covers has ended." I'd like to know if this behavior is configurable? There may be a particular way of thinking about business processes that fits this pattern; however, seeing last week's date on a weekly job that ran today confuses my team, and I'd love to use a flag that makes 1. DAGs run on the start_date 2. DagRun timestamps correspond with the intended actual run date/time.
