<#4191 [Core feature] Execution Date and in case o...
# flyte-github
a
#4191 [Core feature] Execution Date and in case of scheduled execution, execution interval should be set on the execution Issue created by kumare3 Motivation: Why do you think this is important? Currently Flyte does not pass the Execution Date or Execution Interval as part of the execution context.
Execution Date
should be the
timestamp
of when the execution was triggered
Execution Interval
should be the
timedelta
|
interval
for the schedule. For example
1 hour
24 hour
etc? This is currently set as
now()
in flytekit - https://github.com/flyteorg/flytekit/blob/b35af10891929bbeeca091e30dd966aa444e7d93/flytekit/bin/entrypoint.py#L248 But, it should be the actual time of execution Goal: What should the final outcome look like, ideally? This can be set in the flyte-scheduler process when triggering an execution. We could use an
env-var
field to set this value.
Flyteadmin
can check for the existence of this field and in its absence set it to the scheduling time. Flytekit can then default set it from the env-var if available else default it to now. This will also be added to the Agent message, which can created contextvars local current_context, which makes it portable across local and remote. Describe alternatives you've considered NA Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte