You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have scheduled pipeline run, which runs daily on pre-prod to check the environment is good. The team needs the consolidated historical report. I have stored the daily run report in s3, downloaded the report before every execution starts to .tmp folder and uploaded the final consolidated report to s3 after the test run completed. The download report updates the date as the current date and time instead of the actual execution date and time for the past run features.
Describe the solution you'd like
If we store the execution date and time in output json metdata. Then we can use the meta data to populate the actual execution date and time.
Describe alternatives you've considered
I have used the Device field in metadata to store the actual execution date and time for past and current features.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have scheduled pipeline run, which runs daily on pre-prod to check the environment is good. The team needs the consolidated historical report. I have stored the daily run report in s3, downloaded the report before every execution starts to .tmp folder and uploaded the final consolidated report to s3 after the test run completed. The download report updates the date as the current date and time instead of the actual execution date and time for the past run features.
Describe the solution you'd like
If we store the execution date and time in output json metdata. Then we can use the meta data to populate the actual execution date and time.
Describe alternatives you've considered
I have used the Device field in metadata to store the actual execution date and time for past and current features.
Additional context
The text was updated successfully, but these errors were encountered: